> In my experience pre-commit hooks are most often used to generate a starting commit message. The `prepare-commit-msg` hook is a better place to do that as it gives the hook some context about the commit (is the user…
It would be really nice to have this upstream - I don't know if the upstream implementation being in C now makes that easier or harder. As for the license I think because this is so closely based on GPL code it would be…
I like the idea of 'G' to filter hunks. The perl script does not exist since git v2.40.0 so I don't think the installation instructions work for recent versions of git as there is no way to stop 'git add -p' from…
I use an app password but https://github.com/AdityaGarg8/git-credential-email apparently supports OAuth with Gmail, yahoo and outlook
> eval "$CMD" That means you will eval all the filenames, so if you have a file with spaces in it will appear as two files, if there is a `$` in the name it will trigger parameter substitution and so on for the other…
> It’s frustrating that tarball urls are a proprietary thing and not something that was ever standardized in the git protocol. `git archive --remote` will create a tarball from a remote repository so long as the server…
For rebasing `--reapply-cherry-picks` will avoid the annoying fetching you saw. `git backfill` is great for fetching the history of a file before running `git blame` on that file. I'm not sure how much it will help with…
> In my experience pre-commit hooks are most often used to generate a starting commit message. The `prepare-commit-msg` hook is a better place to do that as it gives the hook some context about the commit (is the user…
It would be really nice to have this upstream - I don't know if the upstream implementation being in C now makes that easier or harder. As for the license I think because this is so closely based on GPL code it would be…
I like the idea of 'G' to filter hunks. The perl script does not exist since git v2.40.0 so I don't think the installation instructions work for recent versions of git as there is no way to stop 'git add -p' from…
I use an app password but https://github.com/AdityaGarg8/git-credential-email apparently supports OAuth with Gmail, yahoo and outlook
> eval "$CMD" That means you will eval all the filenames, so if you have a file with spaces in it will appear as two files, if there is a `$` in the name it will trigger parameter substitution and so on for the other…
> It’s frustrating that tarball urls are a proprietary thing and not something that was ever standardized in the git protocol. `git archive --remote` will create a tarball from a remote repository so long as the server…
For rebasing `--reapply-cherry-picks` will avoid the annoying fetching you saw. `git backfill` is great for fetching the history of a file before running `git blame` on that file. I'm not sure how much it will help with…