Use correct commit range for GitHub Actions #10
Merged
Conversation
This file contains 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
wmdietl
changed the title
wmdietl
approved these changes
Dec 31, 2024
There was a problem hiding this comment.
Thanks, looks reasonable.
In eisop/checker-framework#862 you could temporarily check out a branch of this project to make sure it correctly works.
Oh, you mean in the test script? |
In whichever script that clones this repository, you can change it to clone your own branch of this repository. Then you can experiment with changes more quickly. Things seem to work now, but maybe in the future this would be useful. |
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.
#9 Fixes the CI_ORG but not the commit range.
The variable need to be set correctly by adding prefix for Github CI. For example for
EISOP#862,Branches in Github CI is
We should use the following env variable to set them.