(hidden) JCn2rEoOE

words:	0 + 174 = 174
last update:

Linked Mentions (2 in 2 pages)

February 28th, 2022 (1)
- (hidden) DB0HZ5vCF [[(hidden) JCn2rEoOE]]
March 30th, 2022 (1)
- {{[[DONE]]}} teach some [[git-rebase]] stuff to [[(hidden) JCn2rEoOE]]
  - hehe, classic mistake of `git pull` after rebase, instead of `git push --force[-with-leave]`
  - https://stackoverflow.com/questions/9264314/git-commits-are-duplicated-in-the-same-branch-after-doing-a-rebase
  - notes on how to introduce a newbie to `git rebase -i`: [[(hidden) G8LZoKG3P]]
    - ask if they have used vim & are comfortable working with it
      - if no, setup the editor as vscode:
        
        `~/.gitconfig`
        
```shell [core] editor = '/usr/local/bin/code' --wait #editor = '/usr/local/bin/code' --new-window --wait ```

if sending thru slack, put in backticks (``) to avoid slack changing the characters & them ending up broken
- optionally add another alias for `git log` for viewing a graph of commits
  - ```shell [alias] lg = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit ```
  
  if sending thru slack, put in backticks (``) to avoid slack changing the characters & them ending up broken
- now do the actual rebase
  - vscode will probably open the bloated custom editor. no need, get rid of it ("disable rebase editor" & re-launch the rebase if doesn't automatically switch to just raw `git-rebase-todo` text file editing)