Closed benjaminhwilliams closed 4 years ago
- If the branch
pre-commit-autoupdate
exists, mergemaster
into this branch (or should we delete it, along with any associated open PR, and branch again from the current state ofmaster
?). Otherwise, make that branch and check it out.
Suggest delete, ie. just create a new one off HEAD and force-push.
- If the only changes are contained in
.pre-commit-config.yaml
(i.e. version number changes) and the news fragment, then merge?
I would leave auto-merging as out of scope. You want to merge only when tests pass anyway, but you don't want to monitor this from the PR-creating action.
Good points, thanks.
Workflow now more like:
pip install pre-commit
.pre-commit autoupdate
.pre-commit run --all-files
.git checkout -B pre-commit-autoupdate
..misc
news fragment.Useful inspiration here: https://dev.to/browniebroke/auto-update-pre-commit-hooks-with-github-actions-3f84
Write a GitHub action to periodically do the following:
pip install pre-commit
.pre-commit autoupdate
.pre-commit run --all-files
.pre-commit-autoupdate
exists, mergemaster
into this branch (or should we delete it, along with any associated open PR, and branch again from the current state ofmaster
?). Otherwise, make that branch and check it out..misc
news fragment..pre-commit-config.yaml
(i.e. version number changes) and the news fragment, then merge?Some further refinements to that workflow are probably necessary.