Config: Configure test workflow to run on pushes to all branches (#637)

* config: Configure test workflow to run on pushes to all branches * ci: Prevent duplicate workflows to be triggered by both the push and pull_request events * docs: Remove odd test command artifact README.md
Amsterdam-Music-Lab · Dec 7, 2023 · 717657a · 717657a
1 parent b4031c3
commit 717657a
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 6 deletions.
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
@@ -2,10 +2,6 @@ name: Test suite
 
 on:
   push:
-    branches:
-      - main
-      - develop
-  pull_request:
 
 jobs:
   backend-test:

diff --git a/README.md b/README.md
@@ -45,5 +45,3 @@ To stop the containers, press `ctrl-c` or (in another terminal) run
 
 ## Production build
 A production build should define its own `docker-compose.yaml`, making use of the `Dockerfile` of the `backend` and `frontend` environments. It should also define a custom .env file, with safe passwords for the SQL database and the Python backend. Instead of mounting the entire backend and frontend directory and using the development servers, the backend should serve with gunicorn, and the frontend should use a build script to compile static html, css and JavaScript.
-
-# docker-compose --env-file .env-github-actions run client yarn test --watchAll=false
-Original file line number
+Diff line change
@@ Expand Up / @@ -2,10 +2,6 @@ name: Test suite @@
     on:
       push:
-        branches:
-          - main
-          - develop
-      pull_request:
     jobs:
       backend-test:
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
Expand Up		@@ -45,5 +45,3 @@ To stop the containers, press `ctrl-c` or (in another terminal) run

		## Production build
		A production build should define its own `docker-compose.yaml`, making use of the `Dockerfile` of the `backend` and `frontend` environments. It should also define a custom .env file, with safe passwords for the SQL database and the Python backend. Instead of mounting the entire backend and frontend directory and using the development servers, the backend should serve with gunicorn, and the frontend should use a build script to compile static html, css and JavaScript.

		# docker-compose --env-file .env-github-actions run client yarn test --watchAll=false