How do I write a good commit message?
My commit history is full of 'fix', 'update' and 'asdf'. What does a useful commit message look like and does it actually matter?
5 members · 5 questions
First issues, pull requests and maintainers who'll review your code.
My commit history is full of 'fix', 'update' and 'asdf'. What does a useful commit message look like and does it actually matter?
I've been building projects and just saving folders with names like project-final-v3. Every job asks for Git. What problem does it solve that folders don't?
I want to contribute to open source but every repo looks intimidating and I don't know where to start or what's welcome.
Recruiters apparently look at GitHub. Mine is a graveyard of half-finished repos with no descriptions. What should I fix?
I got a merge conflict for the first time and panicked, deleted the branch and started over. What's the correct way to handle one?