You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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
Is there an existing issue for this?
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.
dependabot-core/common/lib/dependabot/config/file_fetcher.rb
Line 9 in ef20a02
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.
The text was updated successfully, but these errors were encountered: