fledge
fledge copied to clipboard
Pull as part of finalize_version()
- [ ] Add
commit_version(pull = FALSE)
- With
pull = TRUE
we would fetch always and always uncommit + commit if behind master
- With
- [ ] Use
pull = push
infinalize_version()
Only if a remote is defined.
I've started working on a PR #408 but I need more info on what you mean by
With pull = TRUE we would fetch always and always uncommit + commit if behind master
If there are more commits on the remote branch
- there might be conflicts, in that case error?
- if not just rebase?
- what means uncommit here? In the code there's uncommit if the last commit was a bump. Here which commits do you think should be undone, the ones from the remote?
We can try the equivalent of git pull --rebase
and see how this works out.
there's relevant code in #408
Perhaps we a higher-level wrapper around pull + bump_version()
+ finalize_version()
?
06cba7f1b641d654ff1b76324f109f07ba4975a0
what would it be called?
Words that come to mind: update (not clear with update_news()
), commit (:upside_down_face: ), sync.
advance()
?
Not too important, since we now have the GHA workflow.