ci: enable workflows for pull-requests

Author: williamdes

.github/workflows/lint-and-analyse.yml

@@ -1,6 +1,15 @@
 name: Lint and analyse files
 
-on: [push]
+on: 
+  push:
+  pull_request:
+    branches:
+      # Branches from forks have the form 'user:branch-name' so we only run
+      # this job on pull_request events for branches that look like fork
+      # branches. Without this we would end up running this job twice for non
+      # forked PRs, once for the push and then once for opening the PR.
+      # Source: https://github.community/t/how-to-trigger-an-action-on-push-or-pull-request-but-not-both/16662/10
+    - '**:**'
 
 jobs:
     lint-php:

.github/workflows/lint-docs.yml

@@ -1,6 +1,15 @@
 name: lint php documentation
-on: [push]
 
+on: 
+  push:
+  pull_request:
+    branches:
+      # Branches from forks have the form 'user:branch-name' so we only run
+      # this job on pull_request events for branches that look like fork
+      # branches. Without this we would end up running this job twice for non
+      # forked PRs, once for the push and then once for opening the PR.
+      # Source: https://github.community/t/how-to-trigger-an-action-on-push-or-pull-request-but-not-both/16662/10
+    - '**:**'
 jobs:
     lint-docs:
         runs-on: ubuntu-latest

.github/workflows/tests.yml

@@ -1,6 +1,15 @@
 name: Run tests
 
-on: [push]
+on: 
+  push:
+  pull_request:
+    branches:
+      # Branches from forks have the form 'user:branch-name' so we only run
+      # this job on pull_request events for branches that look like fork
+      # branches. Without this we would end up running this job twice for non
+      # forked PRs, once for the push and then once for opening the PR.
+      # Source: https://github.community/t/how-to-trigger-an-action-on-push-or-pull-request-but-not-both/16662/10
+    - '**:**'
 
 jobs:
     test-php: