releaser-pleaser/docs
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
..
explanation feat: run one job concurrenlty to reduce chance of conflicts 2025-06-14 13:32:25 +02:00
guides docs: guide for extra-files (#74) 2024-09-25 12:09:27 +02:00
reference feat(gitlab): make job dependencies configurable and run immediately (#101) 2024-11-15 17:51:54 +01:00
tutorials feat: run one job concurrenlty to reduce chance of conflicts 2025-06-14 13:32:25 +02:00
.gitignore docs: setup mdbook (#27) 2024-08-24 16:23:42 +02:00
book.toml docs: add link to github repo 2024-08-25 22:31:39 +02:00
changelog.md docs: setup mdbook (#27) 2024-08-24 16:23:42 +02:00
introduction.md docs: setup mdbook (#27) 2024-08-24 16:23:42 +02:00
SUMMARY.md feat: run one job concurrenlty to reduce chance of conflicts 2025-06-14 13:32:25 +02:00