79 private links
A cli wrapper combining git and dvs. Instead of doing first dvc commit
then git commit
then individual pushes you can just do it with one fds commit
.
Similarly with fds status
which is probably the most used command - get a quick at-a-glance overview of current project status for both data and code.
By being built as a wrapper it of course still allows delving into the individual programs for more advanced operations. Pretty clever, actually!
Update multiple repositories in with one command.
Similar to git-xargs but seems to work for repositories not hosted on Github. Takes any kind of script and applies it to all repositories you pass in. Very nice! Only the name is a bit worse.
Very interesting, the name basically gives the game away.
You give the tool a list of git(hub) repositories and a command (or more advanced script files) and it runs it against them.
You could for example create a file in each one. Or change some variable. Or grep and sed something from one thing to another thing. Or or or.
Honestly not seeing myself using it that often - but the fact it exists is fascinating to me, and the naming is just genius. Though I am a little sad that it seems to only work for Github projects.
A walkthrough of the most used functions and setup for git annex. In-depth explanations of the how but not the why - use whenever you already know a use-case for git annex.
An in-depth write up of what git annex is, how to use it and (importantly) why. Explains backup and file location scenarios.
Open-source version control system for Data Science and Machine Learning projects. Git-like experience to organize your data, models, and experiments.
A way to track data - even if it is in different locations - alongside code, mimicking its version control. Seems a little complicated but really useful, especially with additional features like data pipelines that are contained
One step to check out github pull (and I believe gitlab merge) requests locally:
git fetch origin pull/1234/head:pr-1234
- origin is the remote origin you want to pull from, the one pull requests have been done against (e.g. your own repository if others have created pull requests there)
- pull/1234/head should have the number of the pull request you want
- :pr-1234 is the local branch you will create - it has to be a new branch
Commandline tool for gitea, can show issues, pull requests, and more.
Very helpful steps for first locating an old file in your git history you only roughly remember the name of, then browsing through its history, then finding exactly what you want.
"🤖 A decorated enhanced elegant, feature rich and modern private git ui repository viewer"
Looks a little like a debloated gitea (which is already quite a debloated gitlab). Nice to look at, only made for browsing so no interaction, pull request, users, issues, merge requests, wiki, etc.
But a nice branch network graph and commit logs, README preview and repository browser.
A complete game centered around grasping the concepts of git. You can interact with it like a 'card-game' or use an integrated git terminal to learn it like on the commandline.
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.
Nice example-driven explanation of got contribution workflow through mail and patches.
A really nice way of using gitlab ci to build images for multiple arches (especially arm and amd64).
Find the commit that introduced a bug in your code: how to use git bisect in 7 steps – flavia bastos
git bisect usage:
git bisect start
> puts you into bisect mode
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.
git bisect reset
> get out of bisect mode
Github cicd based workflow for static website blog comments
Intermediate to advanced git tips:
advanced git log output, digging into individual git ref logs, using git for word-wise diffs (could be really useful for prose!), signing commits, git aliases, and more.
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
Git Server in Docker. Contribute to jkarlosb