Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow dependabot configuration file to live somewhere other than .github/dependabot.{yml/yaml} #6894

Open
1 task done
DaleMckeown opened this issue Mar 23, 2023 · 0 comments
Labels

Comments

@DaleMckeown
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Feature description

Currently dependabot enforces the dependabot configuration file to reside in one of two locations - .github/dependabot.{yml/yaml}.

I have use case where, due to repository size/complexity, I am looking to consolidate a number of automation-related tasks and configurations into a single Automation folder. This will help to keep my repository clean and tidy, with a clear seperation of concerns for automated config/scripts.

tinglesoftware/dependabot-azure-devops#575

This file specifically is causing the block.

CONFIG_FILE_PATHS = %w(.github/dependabot.yml .github/dependabot.yaml).freeze

I propose that the file be modified to have the file paths passed in via config, and an option added to allow a custom file location for the configuration to be added.

@DaleMckeown DaleMckeown added the T: feature-request Requests for new features label Mar 23, 2023
@DaleMckeown DaleMckeown changed the title Allow dependabot configuration file to live somewhere other than .github/dependabot.{yml/yaml} Allow dependabot configuration file to live somewhere other than .github/dependabot.{yml/yaml} Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants