Rebasing across branches

When rebasing a complicated history across branches, run rebase on Github UI (website) as a pull request

• Local rebasing has a limited view to show the diffs.
• Can avoid local branch getting stale vs remote when rebase is executed on the remote (website) directly via a pull request.
  • When you spend a lot of time rebasing to a stale branch just to find out that you need to rebase again to the latest, you'd feel demoralized.

This strategy is also useful when two branches with edits to the same location have a race condition:

• Push sequentially to origin.
• Pull request one of the branches onto the remote and merge it in.
• Then pull request another branch.

Diffing Commits in Github

https://github.com/{user}/{repository}/compare/{pull-to-commit}...{pull-from-commit}

Github Actions

Cache

Managing Github cache via website UI.

https://github.com/<OWNER>/<REPO>/actions/caches

Transfer Repository

How to transfer the repository to another organization or user

Repository URL > Settings > General > Transfer Ownership

All links to the previous repository location are automatically redirected to the new location

• However, to avoid confusion, update any existing local clones to point to the new repository URL