releaser-pleaser/.github
Julian Tölle 906fcb3467 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 15:40:50 +02:00
..
actions/setup-mdbook chore: setup renovate (#64) 2024-09-21 13:29:26 +02:00
workflows feat: run one job concurrenlty to reduce chance of conflicts 2025-06-14 15:40:50 +02:00
renovate.json5 chore(config): migrate config .github/renovate.json5 (#186) 2025-06-07 16:40:56 +00:00