DO NOT MERGE — probe: does the dependabot.yml validator catch the pre-#100 config? - #105
Closed
bgard68 wants to merge 1 commit into
Closed
DO NOT MERGE — probe: does the dependabot.yml validator catch the pre-#100 config?#105bgard68 wants to merge 1 commit into
bgard68 wants to merge 1 commit into
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
Sign up for freeto 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.
Throwaway. Will be closed as soon as checks report — do not merge.
Restores
.github/dependabot.ymlexactly as it stood onmainbefore #100 (the version withversioning-strategy,prefix-development, anddependency-typeon the NuGet block) to answer one question:Does GitHub's
.github/dependabot.ymlcheck run on, and fail for, that config?The answer decides how much the guard being added needs to do. If the validator fails here, invalid keys cannot silently reach
mainthrough a PR again and the guard only needs to cover the harder case — a config that parses but still is not being applied. If it passes, then nothing catches this and the guard carries the whole load.