4 points
git is a blockchain without a proof of work
2 points
The proof of work is the commit content itself! Unlike some arbitrary brute force task of no value.
2 points
5 points
*
- Make Structured Commits by context
- Make a MR
- Forgot to Rebase
- Close MR
- Rebase
- Make a MR
- Forgot to push the Rebase so now all Rebase items are on my MR
- Close MR
- Reset Changes
- Push Rebased Items
- Make Structured Commits,
- Forget a file
- Reset Changes
- Make a mega Commit
- Make a MR
- Pipeline fails
1 point
I’ve been using git for 20 years and have no idea how it works. Probably will be the next things I will do a deep dive into.
2 points
4 points
This one must be the person recruiters have in mind when they list multiple years of experience with technology that just came out in their job postings.
2 points
5 points
I stand by my opinion that git should be the what VCS software uses internally and is built on. It’s an API for VCS developers to use. And repon admins.
Thev actual VCS should have it’s own API and CLI that is intuitive and shouldn’t require understanding the underlying data structure.
3 points
force push for release
