Repository navigation
aeon-update: treat .github/dependabot.yml as operator-owned - #1194
Merged
Merged
Conversation
Instances dropped their dependabot.yml (aeon-agent#257, miroshark-aeon#203) since they only duplicated canon Dependabot PRs. Classify the file as operator-owned so aeon-update surfaces upstream changes instead of writing it back into an instance.
2 tasks done
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
1 participant
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.
Instances dropped their
.github/dependabot.yml(aaronjmars/aeon-agent#257, aaronjmars/miroshark-aeon#203) because it only duplicated the Dependabot PRs canon already gets.This marks the file as operator-owned in aeon-update, so upstream changes to it are surfaced in the update PR body instead of being written back into an instance.
Change is in place (same line count), so no eyebrow line shift and no catalog regen.