Open lorenzwalthert opened 1 year ago
I think that detecting hook-dependency-update
merges to main
would be easy and transparent in a github action
There are some workflows that automatically bump R package versions that we could in tandem, so that both R version and tag creation was automated every time that branch is merged to main
This could be skipped with keywords on PR title (such as [skip-tag]). I could try to set up POC on a forked repository to better evaluate.
tags must be on main branch to be recognised with pre-commit autoupdate. Does it work if we tag on branch hook-dependency-update and then merge to main?
This is an easy test for the next merge. I think that tags are not branch-context-dependent, but I'd have to a have a thorough look at the git documentation.
There is already a template: https://github.com/lorenzwalthert/precommit/blob/main/.github/workflows/hook-release.yml.
Also, the functionality is already in release_gh()
function. It contains multiple steps. If you want ot have a go, it would be appreciated. 👍
hook-dependency-update
was merged intomain
. But probably easier is just as part of the hook dependency update. Also belongs together semantically.release_gh()
works locally currently.main
branch to be recognised withpre-commit autoupdate
. Does it work if we tag on branchhook-dependency-update
and then merge tomain
?