-
Notifications
You must be signed in to change notification settings - Fork 8
Closed
Copy link
Labels
part:ciAffects the GitHub workflow and other parts for running CIAffects the GitHub workflow and other parts for running CIpart:templateAffects the cookiecutter template filesAffects the cookiecutter template filespart:toolingAffects the development tooling (CI, deployment, dependency management, etc.)Affects the development tooling (CI, deployment, dependency management, etc.)
Milestone
Description
Instead of manually updating all repos with the auto-dependabot.yaml workflow, we should:
- Add the
auto-dependabot.yamlworkflow to repo-config - Update the migrate script to:
- Install/replace any existing workflow with the same name
- Fix the ownership file (CODEOWNERS) as needed
Benefits
- Centralized management of the workflow
- Consistent deployment across all repos
- Automated updates via repo-config migrate script
- Can be tested in one repo before deploying everywhere
Current Status
Multiple PRs have been created manually to update existing workflows:
- 12 PRs currently open across frequenz repos
- 3 PRs already merged
Proposed Approach
- Add the workflow template to repo-config with the correct format:
- uses: frequenz-floss/dependabot-auto-approve@005e52004f5d5c6af2f81b89ec25e5cf6f3dfd77 # v1.3.0
- Update migrate script to handle workflow installation/replacement
- Update migrate script to fix CODEOWNERS if needed
- Test in one repo first
- Deploy via repo-config to all repos
Related
This would supersede the manual PR updates currently in progress.
Metadata
Metadata
Assignees
Labels
part:ciAffects the GitHub workflow and other parts for running CIAffects the GitHub workflow and other parts for running CIpart:templateAffects the cookiecutter template filesAffects the cookiecutter template filespart:toolingAffects the development tooling (CI, deployment, dependency management, etc.)Affects the development tooling (CI, deployment, dependency management, etc.)