Use explicit path for GitHub Actions workflows in Dependabot configuration #923
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
…ation The path of the dependencies manifest files must be defined in the Dependabot configuration for each "package ecosystem" entry. When implementing support for managing GitHub Actions workflows dependencies, the Dependabot developers made the inexplicable decision that, unlike any other ecosystem, Dependabot would look for the workflows under the `.github/workflows` subfolder of the specified path, rather than the actual path that is provided. Support for actually using the path specified by the configuration was later added. Since the configuration required by the original behavior was quite unintuitive, it is hereby changed to the actual path of the workflows in the repository.
per1234
added
type: enhancement
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.
The path of the dependencies manifest files must be defined in the Dependabot configuration for each "package ecosystem" entry. When implementing support for managing GitHub Actions workflows dependencies, the Dependabot developers made the inexplicable decision that, unlike any other ecosystem, Dependabot would look for the workflows under the
.github/workflowssubfolder of the specified path, rather than the actual path that is provided. Support for actually using the path specified by the configuration was later added (dependabot/dependabot-core#6189).Since the configuration required by the original behavior was quite unintuitive, it is hereby changed to the actual path of the workflows in the repository.