docs: Link to GitHub Actions docs (#298)

* docs: link to GitHub Actions docs

* fix suggestion

* Apply suggestions from code review

---------

Co-authored-by: Jan Amann <jan@amann.work>

Author: Lightning00Blade

README.md

@@ -29,8 +29,9 @@ on:
   pull_request_target:
     types:
       - opened
-      - edited
       - reopened
+      - edited
+      # - synchronize (if you use required Actions)
 
 jobs:
   main:
@@ -169,6 +170,10 @@ There are two events that can be used as triggers for this action, each with dif
 1. [`pull_request_target`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#pull_request_target): This allows the action to be used in a fork-based workflow, where e.g. you want to accept pull requests in a public repository. In this case, the configuration from the main branch of your repository will be used for the check. This means that you need to have this configuration in the main branch for the action to run at all (e.g. it won't run within a PR that adds the action initially). Also if you change the configuration in a PR, the changes will not be reflected for the current PR – only subsequent ones after the changes are in the main branch.
 2. [`pull_request`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#pull_request): This configuration uses the latest configuration that is available in the current branch. It will only work if the branch is based in the repository itself. If this configuration is used and a pull request from a fork is opened, you'll encounter an error as the GitHub token environment parameter is not available. This option is viable if all contributors have write access to the repository.
 
+> [!TIP]
+> If the workflow is required for merging, you need to ensure that the you add a trigger type for [`synchronize`](https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=synchronize#pull_request).
+> This will ensure that the check is ran on each new push as required workflows need to run on the lastest change.
+
 ## Outputs
 
 - The outputs `type`, `scope` and `subject` are populated, except for if the `wip` option is used.