chore: Skip check-version-bump ci job in forks #15959
Merged
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.
What does this PR try to resolve?
I occasionally open PRs in my fork to test CI for work in progress changes. (Trying to avoid spamming notifications to the t-cargo members)
The
check-version-bump
job makes assumptions that the fork has an up to date list of release tags.My fork (and I am guessing most others) does not contain the release tags so this CI job fails, which is a minor papercut.
My solution is to only run
check-version-bump
in PRs torust-lang/cargo
and skip in forks.How to test and review this PR?