-
Notifications
You must be signed in to change notification settings - Fork 63
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
CI: Check for uncommitted table alteration #27
Merged
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
Before, the checks would always indicate a failure, although the scenarios are not intended to succeed. Now, they will only fail on an unchanged `table.md` despite a different outcome in the scenario run. Co-authored-by: Anderson Bravalheri <[email protected]>
chrysle
force-pushed
the
ci-check-table-alteration
branch
3 times, most recently
from
April 19, 2024 19:27
c10475a
to
8333e87
Compare
Before, the checks would always indicate a failure, although the scenarios are not intended to succeed. Now, they will only fail on an unchanged `table.md` despite a different outcome in the scenario run. Co-authored-by: Anderson Bravalheri <[email protected]>
chrysle
force-pushed
the
ci-check-table-alteration
branch
from
April 19, 2024 19:35
8333e87
to
33bfbdf
Compare
abravalheri
approved these changes
Apr 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @chrysle . I think that is a nice way of checking for this repository.
chrysle
force-pushed
the
ci-check-table-alteration
branch
from
April 20, 2024 06:59
ff57915
to
49ebd06
Compare
@pradyunsg Gentle ping. |
webknjaz
reviewed
Apr 28, 2024
…ci-check-table-alteration
Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <[email protected]>
chrysle
force-pushed
the
ci-check-table-alteration
branch
from
April 28, 2024 13:20
ef5868f
to
5095dcd
Compare
webknjaz
reviewed
Apr 29, 2024
And use better syntax to append to `GITHUB_OUTPUT`. Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <[email protected]>
pradyunsg
approved these changes
Apr 29, 2024
Thank you all for reviewing! |
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.
Before, the checks would always indicate a failure, although the scenarios are not intended to succeed. Now, they will only fail on an unchanged
table.md
despite a different outcome in the scenario run.I also plan to schedule the run, so that the compatibility matrix is kept up-to-date.
Closes #26.