Create a .github/dependabot.yml file from a compact JSON definition. Each update block is checked for a supported package ecosystem, absolute directory, schedule interval, and practical pull-request limits before valid YAML is emitted.
The generator maps camelCase JSON options to Dependabot keys and emits one update block for each ecosystem and directory pair.
Commit the result as .github/dependabot.yml on the default branch. Dependabot reads configuration only from that location.
Try the sample input built into the page. The result uses the same validation and export path as pasted content.
{"updates":[{"ecosystem":"npm","directory":"/","interval":"weekly","openPullRequestsLimit":5},{"ecosystem":"github-actions","directory":"/","interval":"monthly"}]}Supported fields include ecosystem, directory, interval, day, time, timezone, targetBranch, openPullRequestsLimit, labels, reviewers, and assignees.
Repository-specific registries and advanced groups are not generated. Add them manually when private dependencies or grouped updates are required.
Use the format shown in the sample. The page validates required fields and reports malformed lines or values before producing output.
No. Processing happens in your browser and the core function makes no network request.
Yes, after reviewing repository-specific names, permissions, paths, and policies that a browser-only tool cannot verify.
Hosted services may apply repository context, current platform rules, presets, or permissions that are unavailable to this local check.
Yes. The input and downloaded files use UTF-8, although the target format may impose narrower naming or syntax rules.
| Item | Meaning |
|---|---|
| Output | Copy-ready YML or text |
| Processing | Local browser execution |
| Network | Not required |
Browse generators, parsers, validators, and helpers for Git configuration and repository workflows.
View category