find a way to early exit release workflow if commits won't trigger a release
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
https://github.com/openedx/paragon/blob/release-22.x/.github/workflows/release.yml has to go through all of
just to see that a chore: commit was pushed and no new release should be made.
it'd be great (from a saving time and saving carbon stand point) to be able to skip all of that and just end the workflow if we aren't trying to release the changes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/release.yml on the release-22.x branch and compare it with the referenced version at lines 13-34. Trace how the workflow determines whether a release is needed for a chore: commit, then identify where it can exit earlier. Done means non-release commits skip the remaining release work while release-triggering commits retain the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100