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

Feature request: use config from dependabot.yml #279

Open
timstibbs-hippo opened this issue Feb 15, 2024 · 1 comment
Open

Feature request: use config from dependabot.yml #279

timstibbs-hippo opened this issue Feb 15, 2024 · 1 comment

Comments

@timstibbs-hippo
Copy link

timstibbs-hippo commented Feb 15, 2024

Use case: my dependabot.yml config isn't doing quite what I expected, so I'd love to be able to run that locally against my local branch to test out the effect of different config options.

I suspect that the job.yaml file can do everything that you can do in dependabot.yml, however the two are different. This prevents you using this CLI to build your dependabot.yml file. If we could support fetching config from dependabot.yml, then you'd be able to use the same file both locally and on github.

To illustrate this, I'm imagining running the following command:

dependabot update <ecosystem> dummy/repo --local . --config .github/dependabot.yml

Even better if it could pick up that file automatically, but I realise this might be challenging from a backwards compatibility perspective.

Note that I don't have a good understanding of the differences of the capabilities of job.yaml vs dependabot.yml, so this suggestion might essentially be impossible.

Note also that this is related to, but not the same as: #59. Would also potentially satisfy dependabot/dependabot-core#4605.

@denisstrelnikov
Copy link

Agree👍
From what I understand, the dependabot.yaml file is converted in runtime into a job.yaml-like layout under the hood by GitHub's dependabot. Therefore, why can't we just use dependabot.yaml everywhere, as it has good official documentation, unlike job.yaml?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants