No description
|
popebob
d49f88e5a2
Add info for writing better commit messages
Not always something I'm personally that great at, but this particular article has made me make conscious effort to sensibly document my commits. |
||
|---|---|---|
| docs | Separate documentation | |
| media | Initial import, sanitized for your satisfaction | |
| bash-functions | Initial import, sanitized for your satisfaction | |
| bash-git_prompt | Split prints to add comment for clarity | |
| git-aliases | Initial import, sanitized for your satisfaction | |
| README.md | Add info for writing better commit messages | |
Contents of this Repository
- README.md - This README
- bash-functions - File that contains some example functions
- bash-git_prompt - An example colorful prompt for bash to show git status
- git-aliases - Some example aliases for
~/.gitconfig - docs/quick-start.md - Quick start guide for git
- docs/helpers.md - Docs for helper tools
Examples and more information about bash-functions, bash-git_prompt and git-aliases below the Getting Started guide.
More information about branching, forking, rebasing, merging and all that good stuff can be found in this excellent (and free!) online book: https://git-scm.com/book/en/v2
Information on how to write better git commit messages, as well as explanations of why you might want to: https://chris.beams.io/posts/git-commit/