Changed Workflow Trigger #232
Open
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
Signed-off-by: Sachin Panayil <[email protected]>
sachin-panayil
requested review from
IsaacMilarky,
natalialuzuriaga and
DinneK
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.
Changed Workflow Trigger
Problem
I noticed that every push to main triggered a Repolinter PR to be setup. This seemed redundant as only once pass through of the repolinter checks should be necessary. After that, it should be triggered manually only.
Solution
Wrote a small script that uses the label
repolinter-initializedto track if a Repolinter Results PR was sent for the first time. After its been sent for the first time, the workflow can only be triggered manually.Result
Unnecessary PRs will no longer be sent and the PR will have the
repolinter-initializedlabelTest Plan