Read on Twitter
Order of operations for getting code from local to merged into main:
1. Commit early; commit often - write the random useless commit message that makes sense at the time.
https://abs.twimg.com/emoji/v2/... draggable="false" alt="đź’ˇ" title="Elektrische GlĂĽhbirne" aria-label="Emoji: Elektrische GlĂĽhbirne">If you know it& #39;s a temporary commit, add that to the message! I use "squash/drop this commit - {context}"
1. Commit early; commit often - write the random useless commit message that makes sense at the time.
2. Open a draft PR - Give yourself a todo list and start putting your path up for your team to see. Getting feedback early in your process will reduce your cognitive load when it& #39;s time for CR. https://abs.twimg.com/emoji/v2/... draggable="false" alt="đź’ˇ" title="Elektrische GlĂĽhbirne" aria-label="Emoji: Elektrische GlĂĽhbirne">Seeing code diff in a GUI can help you catch mistakes/optimizations before others
3. Amend commits - forgot to lint and missed a console.log? `git commit --amend --no-edit` is your friend. Just append that change to your previous commit and you& #39;re good!https://abs.twimg.com/emoji/v2/... draggable="false" alt="đź’ˇ" title="Elektrische GlĂĽhbirne" aria-label="Emoji: Elektrische GlĂĽhbirne">I also use this so my colleagues don& #39;t notice when I& #39;ve made a dumb error that I caught myself
4. Rebase often - This is not only to avoid merge commits! This is the biggest reason "it works on my machine" is a meme in swe tech. Things can happen that you might not see and a CI might not catch either. https://abs.twimg.com/emoji/v2/... draggable="false" alt="đź’ˇ" title="Elektrische GlĂĽhbirne" aria-label="Emoji: Elektrische GlĂĽhbirne">This reduces your feedback loop on a PR so you catch your own bugs
5. Squash and drop - Rebase your branch using the interactive argument. This allows you to see how you& #39;ve organized your commits and make small changes (remember when you noted to yourself to squash that commit?) https://abs.twimg.com/emoji/v2/... draggable="false" alt="đź’ˇ" title="Elektrische GlĂĽhbirne" aria-label="Emoji: Elektrische GlĂĽhbirne">You can also rewrite commit messages that no longer make sense
6. Reorganize - Reset your branch (after rebasing!!) if your commit structure feels difficult to review. Do your commits accurately reflect what you would do NOW if you had the same context when you started? https://abs.twimg.com/emoji/v2/... draggable="false" alt="đź’ˇ" title="Elektrische GlĂĽhbirne" aria-label="Emoji: Elektrische GlĂĽhbirne">Help colleagues review faster by giving them a good commit structure
