releaser-pleaser/docs/tutorials
Julian Tölle 3ff0cce003 feat: run one job concurrenlty to reduce chance of conflicts
Each run of releaser-pleaser acts on the same global state in the
forge. Therefore parallel runs are unnecessary.

This commit also communicates to the GitHub and GitLab CI pipelines that
the releaser-pleaser jobs can be cancelled as early as possible.

- On GitHub Actions this can be guaranteed through the workflow
  settings. These settings are copied into each repository that uses
  releaser-pleaser, so users need to update this manually. I will add a
  note to the release notes for this.
- On GitLab CI/CD this requires the user to configure a project level setting to
  "auto-cancel redundant pipelines". We will not recommend user to set
  this, as it is quite invasive and can break their regular CI pipelines.
2025-06-14 13:32:25 +02:00
..
github-settings-pr.png docs: add all current features (#34) 2024-08-25 22:13:56 +02:00
github-settings-workflow.png docs: add all current features (#34) 2024-08-25 22:13:56 +02:00
github.md feat: run one job concurrenlty to reduce chance of conflicts 2025-06-14 13:32:25 +02:00
gitlab-access-token.png docs: GitLab tutorial and CI/CD component reference (#72) 2024-09-25 11:23:04 +02:00
gitlab-settings-merge-method.png docs: GitLab tutorial and CI/CD component reference (#72) 2024-09-25 11:23:04 +02:00
gitlab-settings-squash.png docs: GitLab tutorial and CI/CD component reference (#72) 2024-09-25 11:23:04 +02:00
gitlab.md feat(gitlab): support self-managed instances (#75) 2024-09-25 12:41:11 +02:00