79 private links
Sync github, bitbucket, and trac issues with taskwarrior
supports many more than tagline above
I came across this exact issue while trying to come up with a solid set of flags to use with ctrlp in vim. I ended up settling on rg --hidden --glob '!.git'
which does what I want and, since it lives in my .vimrc, I don't mind the verbosity. I do think it's surprising to find rg searching through the .git directory but I can also understand the mental model of rg not wanting to be "git aware" or any other VCS for that matter.
Store your Notes in any Git Repo. simple mobile app to take notes, and sync with any git repo (github/-lab/gitea/ssh/...)
Syncing folders with Git Sync and Systemd
[50:00]
Understanding underlying structure of git:
- content addressable filesystem
- blobs and trees
- tags and branches as refs
- what does branching do
- what does merging do
- what does resetting do
- how to use the reflog to revert local actions
Gitless: a simple version control system built on top of Git
Automatically commits on saving and might be better suited for prose workflows?
Safe and simple one-script git synchronization.
Idea is continuous history (a la gopass git) -- it's not a pretty history, but it automatically syncs on filechanges.
Good-lookin' diffs. Actually… nah… The best-lookin' diffs. :tada: - so-fancy
Reading Time: 5 minutes Git’s push --force is destructive because it unconditionally overwrites the remote repository with whatever you have locally, possibly overwriting any changes that…
Additional Information on Undoing things in git: https://git-scm.com/book/en/v2/Git-Basics-Undoing-Things
Commit history (preferably of a non-pushed path, since it rewrites hashes) can be edited; useful for feature branches with useless commits / debug messages / strange orders and so on -- things which happen during committing, but should not stay in the end-product.
- best article: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
- why squash?: https://jamescooke.info/git-to-squash-or-not-to-squash.html
- rebasing basics: https://git-scm.com/book/en/v2/Git-Branching-Rebasing
- some workflow recommendations: http://justinhileman.info/article/changing-history/
- additional tips (mostly covered in first link tho): https://www.maykinmedia.nl/blog/2017/nov/20/git-rebasing-make-your-commit-history-pretty/
incredible git aliases
excerpts:
- find branches by grepping for parts of their name in your codebase
- get summaries of your own commits and logs since a specific last point in time
- quickly host your own git server to push to, pull from (through gits built in server)
- directly running ci tests/documentation generation/deployments from the commandline through git by using json-parsing and a rest-api
[26:00]
How to avoid merge conflicts in a NEWS or ChangeLog file
An introductory guide and resource for Git hooks. Learn how to use pre-commit hooks, post-commit hooks, post-receive hooks, and more. Created by Matthew Hudson, a programmer experimenting with combing Git + WebHooks + Webpipes.
I have been using LaTeX for a couple of years now, but not until yesterday I combined it with git after reading about this possibility. Here are...