Feat/ga checks #127
Open
Feat/ga checks #127
Conversation
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
kvdblom
requested changes
Nov 27, 2025
Collaborator
kvdblom
left a comment
kvdblom
left a comment
There was a problem hiding this comment.
Very small change, otherwise looks good!
| workflow_dispatch: # allow triggering workflow manually | ||
| inputs: | ||
| reason: | ||
| description: "Reason for Running" |
Collaborator
There was a problem hiding this comment.
Probably good to have a more informative description, maybe something like: "Automatically checking formatting."
Collaborator
Author
There was a problem hiding this comment.
This is just the input prompt. You are supposed to input your reason for running 😉
kvdblom
approved these changes
Nov 27, 2025
Collaborator
|
Looks good, only merge after: #114 |
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.
Adds the GitHub Action responsible for triggering the validation of the new problem
Note that this check is only supposed to be triggered when the template file "new_problem.yaml" is changed. It will mark a failure if the name is not changed, that's why the test currently fails here.
Closes #124