Repository navigation
ci: let a manual release skip its race tests - #65
Merged
Merged
Conversation
Add a skip-tests input to the release workflow's dispatch trigger. It defaults to false. When set, the release still downloads, checks go mod tidy and builds every module, and only leaves out the race tests, for a commit whose CI on main already passed. A release started by a tag push always runs them.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You can now start a release without its race tests:
skip-testsis a boolean on the dispatch trigger and defaults to false. With it on, the release still downloads, checks thego mod tidydiff and builds the root and every sub-module, so a broken build still stops it. Only thego test -raceruns are left out, which saves close to an hour.Use it when CI on
mainalready passed for the commit you're tagging. A release started by pushing a tag always runs the tests, whatever the input says. The value reaches the scripts through an env var, not inline expansion. AGENTS.md describes the option next to the release command.Checked with actionlint.