deiwin

4 ms·

1.
by deiwin 7y ago
How does licensing work for this?
2.
Git better–learn to rewrite history like it’s 1984(medium.com)
4 points by deiwin 8y ago|0 comments
3.
Productionproofing Amazon EKS(medium.com)
4 points by deiwin 8y ago|0 comments
4.
by deiwin 9y ago
Also, the ticket and the commits can provide answers to the same questions without being redundant. The answers are just at a different level of abstraction and for different readers. Tickets usually describe product-level decisions, while
5.
by deiwin 9y ago
What makes you say that? The Focused rule from the article is also meant to persuade you to split the work into similarly concise and focused commits.
6.
by deiwin 9y ago
One Size Fits All, probably.
7.
by deiwin 9y ago
Tying the ticketing system and the repository together is a good idea and definitely worth implementing, but there's a fine balance in deciding what context should be kept in the ticket and what in the code repository. If you put too m
8.
by deiwin 9y ago
Thinking that providing additional context for commits is a waste of time is short-sighted. Yes, it requires more time and effort in the short-term (i.e. for creating the commit), but if it's a complex, long-lived project, then that ex
9.
by deiwin 9y ago
Where did you find the 7 character suggestion? 7 used to be the default suggestion, but the problem of collisions has been acknowledged and dealt with by the git project. Linus himself authored the change that made the abbreviated revisio
10.
by deiwin 9y ago
You're correct. There are more fundamental conditions that have to be met for effective collaboration.
11.
Four rules for effective collaboration – Guidelines for better commits(github.com)
50 points by deiwin 9y ago|35 comments
12.
Improving GitHub reviews with fixup commits and a helpful bot(github.com)
2 points by deiwin 9y ago|0 comments