Archive for 2017
Ever have to update/merge a PR on BitBucket with Mercurial? I couldn't find documentation anywhere, so doing so here:
- hg up BOOKMARK_NAME
- hg merge [--preview] -r REV
- If EDITOR is not set:
export EDITOR=vim
- hg resolve --all
- hg commit -m "Merge with default"
- hg push --allow-anon
Tags: bitbucket, bookmark, control, hg, mercurial, merge, rebase, scm, source
Posted in g33k, tech |
Especially because:
https://github.com/python/cpython/commit/47320a652e872003f3dd3a9db4243067b09dd316#diff-c6a3fa0ad7b17f8e32f340835a4e5353
🙂
Tags: 3.7, path, pathlib, posix, python, python3
Posted in g33k, tech |
So, every now and then on a PR I need to rebase and fix things so I can retest etc. - I always forget this so blogging it to remember.
Scenario:
I have a diff on origin/master on my forked repo and I need a rebase from upstream/master (where I forked from).
Process:
Github recommends merging (https://help.github.com/articles/syncing-a-fork/), this is not always the best way. I do the following:
- git remote add upstream https://github.com/python/cpython.git
- git fetch upstream master
- git rebase upstream/master (no space here '/' instead)
I hope this saves you some time as I continually waste time here.
Tags: git, github, rebase, upstream
Posted in g33k, linux, tech, Uncategorized |