Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

github: only run a single workflow at a time #41

Merged
merged 1 commit into from
Oct 2, 2024

Conversation

crawford
Copy link
Contributor

This serves two purposes:

  • cuts costs by canceling CI when pull requests are updated
  • prevents issues when releasing after pull requests are merged

Elaborating on that second point, two tags are pushed, so two release workflows are started as a result. The earlier one takes longer to run, however, and mutates the 'latest' tag last. This is a great example of the dangers of mutability.

This serves two purposes:

- cuts costs by canceling CI when pull requests are updated
- prevents issues when releasing after pull requests are merged

Elaborating on that second point, two tags are pushed, so two release
workflows are started as a result. The earlier one takes longer to
run, however, and mutates the 'latest' tag last. This is a great
example of the dangers of mutability.
@crawford crawford merged commit a1635fc into edgebitio:main Oct 2, 2024
3 checks passed
@crawford crawford deleted the cancel branch October 2, 2024 16:08
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.

2 participants