Make workflows not trigger twice on pushes to PRs (#364)

* Do not trigger twice on PRs, add workflow_dispatch to run manually

* Add comment to run the workflows manually

.github/workflows/edm4hep.yaml

@@ -1,6 +1,11 @@
 name: edm4hep
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+    - master
+  pull_request:
+  workflow_dispatch:
 
 jobs:
   build-and-test:

.github/workflows/key4hep.yml

@@ -1,6 +1,12 @@
 name: key4hep
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+    - master
+  pull_request:
+  workflow_dispatch:
+
 jobs:
   build-and-test:
     runs-on: ubuntu-latest

.github/workflows/pre-commit.yml

@@ -1,6 +1,11 @@
 name: pre-commit
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+    - master
+  pull_request:
+  workflow_dispatch:
 
 jobs:
   pre-commit:

.github/workflows/sanitizers.yaml

@@ -1,6 +1,12 @@
 name: sanitizers
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+    - master
+  pull_request:
+  workflow_dispatch:
+
 jobs:
   build-and-test:
     runs-on: ubuntu-latest

.github/workflows/test.yml

@@ -1,6 +1,12 @@
 name: linux
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+    - master
+  pull_request:
+  workflow_dispatch:
+
 jobs:
   build-and-test:
     runs-on: ubuntu-latest

.github/workflows/ubuntu.yml

@@ -1,6 +1,11 @@
 name: ubuntu
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+    - master
+  pull_request:
+  workflow_dispatch:
 
 jobs:
   test:

README.md

@@ -164,6 +164,13 @@ After compilation you can run rudimentary tests with
 
     make test
 
+## Running workflows
+To run workflows manually (for example, when working on your own fork) go to
+`Actions` then click on the workflow that you want to run (for example
+`edm4hep`). Then if the workflow has the `workflow_dispatch` trigger you will be
+able to run it by clicking `Run workflow` and selecting on which branch it will
+run.
+
 ## Advanced build topics
 
 It is possible to instrument the complete podio build with sanitizers using the