feat: add force-configcheck annotation to trigger configcheck manually#221
Merged
Merged
Conversation
aa1ex
force-pushed
the
feat/force-configcheck-annotation
branch
from
July 7, 2026 10:42
ce1bb97 to
5b4140e
Compare
Include annotation value in pipeline hash so changing it triggers configcheck even when spec is unchanged. Uses omitempty for backward compatibility — existing pipelines without the annotation are unaffected. Signed-off-by: Aleksandr Aleksandrov <aaleksandrov.cy@gmail.com>
aa1ex
force-pushed
the
feat/force-configcheck-annotation
branch
from
July 7, 2026 12:57
5b4140e to
9946c0b
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Include annotation value in pipeline hash so changing it triggers configcheck even when spec is unchanged. Uses omitempty for backward compatibility — existing pipelines without the annotation are unaffected.