Interact with a git repositoriy's bugs (i.e. bug-tracker) through the commandline without needing to rely on hosted offerings like gitlab or github. At the same time allows interacting with such offerings through the bug bridges.
git bisect bad <commitref|HEAD> > signal to git the commit where things definitely don't work right anymore (mostly HEAD)
git bisect good <commitref|HEAD> > signal to git the commit where things definitely did work right still (can be any number of commits back).
You will no be put into a special bisect inspection mode and git will checkout various commits in a divide and conquer manner for you to declare their status.
git bisect good|bad > After checking the state of the app/running tests/whatever, declare the commit as working or not-working. Git will then move you to the next commit until you find the right one introducing the bug.
ForgeFed is an upcoming federation protocol for enabling interoperability between version control services. It’s built as an extension to the ActivityPub protocol, allowing users of any ForgeFed-compliant service to interact with the repositories hosted on other instances.
Using it could enable building federated repository / vcs systems mirroring github/gitlab, or other implementations
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.
FoldFold allExpandExpand allAre you sure you want to delete this link?Are you sure you want to delete this tag?
The personal, minimalist, super-fast, database free, bookmarking service by the Shaarli community