do you have rules for using `git merge` you follow? what are they? (similar to these "rules for rebase" social.jvns.ca/@b0rk/111540871)

so far my ideas are:

* merge `main` into your branch periodically so it it doesn't get too far behind
* something about avoiding "foxtrot" merges so that the first parent makes sense (blog.developer.atlassian.com/s)
* if you resolved a merge conflict wrong, undo it right away (?)

Follow

@b0rk Merge upstreams only. Test merges immediately and push them before doing further work. If the merge can't be pushed due to non-ff, redo the merge. I don't want to work with anything more complicated than 2 parallel histories with merges syncing them.

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!