Skip to content

Use cancel-in-progress instead of styfle/cancel-workflow-action.#2085

Open
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_943469061
Open

Use cancel-in-progress instead of styfle/cancel-workflow-action.#2085
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_943469061

Conversation

@copybara-service

Copy link
Copy Markdown
Contributor

Use cancel-in-progress instead of styfle/cancel-workflow-action.

Advantages:

  • We don't need to grant write permissions to a third-party action (or even use it at all).
    • Not that I have any reason to think it's likely to be a problem, but strange things happen sometimes.
  • One less action means one less thing for us to merge Dependabot updates for.
  • The new approach can easily allow CI for merged trunk commits to continue even after other trunk commits are merged, while still stopping PR CI when new changes are pushed.
    • This is especially nice because cancellations (at least those from styfle/cancel-workflow-action, maybe in general) show up as failures. It's nice to be able to pick out real failures (e.g., those fixed by cl/925609698 and cl/943404496) without sorting through cancellations.
  • All else being equal, it's nice to have smaller, simpler configuration.

Assuming that this approach holds up, I'll replicate it to our other projects.

RELNOTES=n/a

Advantages:
- We don't need to grant write permissions to a third-party action (or even use it at all).
  - Not that I have any reason to think it's likely to be a problem, but strange things happen sometimes.
- One less action means one less thing for us to merge Dependabot updates for.
- The new approach can easily allow CI for merged trunk commits to continue even after other trunk commits are merged, while still stopping PR CI when new changes are pushed.
  - This is especially nice because cancellations (at least those from `styfle/cancel-workflow-action`, maybe in general) show up as _failures_. It's nice to be able to pick out _real_ failures (e.g., those fixed by cl/925609698 and cl/943404496) without sorting through cancellations.
- All else being equal, it's nice to have smaller, simpler configuration.

Assuming that this approach holds up, I'll replicate it to our other projects.

RELNOTES=n/a
PiperOrigin-RevId: 943469061
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant