Closed
Description
Would it be helpful to enumerate the sections for structure (and have a catchy blog post title?) ?
e.g:
#11 Things You Need to Know Git
- What is Git and Why do I need it?
- init - initialise a folder on your computer as a git repository (would also need to show creating the repo on GitHub)
- clone - make a copy of an existing project (e.g. from GitHub)
- add - add specific files you have changed or all files at once.
- commit - save your work as a version.
- pull - retrieve the changes others have made (updates your local copy of the project)
- push - sends the changes you have made to files/folders to the remote repository
- Checkout / Branching - create a new feature
- merge - Apply the changes you have made to the main repository
- _Resolve_ Merge Conflicts - Inevitably when working in a team...
- Revert - if you want to go back to a previous version of your code. (the power of version control... History.)
Then it makes it easier for others to extend your tutorial with other topics/sections they find useful.
e.g:
- Forking - useful when you want to contribute to someone else's project
- Issues - creating an issue is the easiest way to get started contributing to projects.
- Commenting on commits using line references
- Pull Requests - Collaboration
- History/Blame (see who made what change in the GitHub UI)
- Starring & Watching
- Forcing (should you ever force push a commit?)
- Deleting ("Pruning") branches you no longer need.
- Other Git hosting providers (its not just GitHub...) e.g: BitBucket allows you to have unlimited Private repos for free (provided you have a small team): https://bitbucket.org/plans
This way the contributors to your repository/tutorial could discuss and vote on the ordering of the sections and easily propose new ones or expand on existing...
If it got to the point that you had an exhaustive list of GitFu The 67 things you need to know Git your post will move from being a "beginner" post to the Number 1 linked to & starred tutorial on the internet (hacker news, reddit, etc.)
Again, just a suggestion... 👍
Metadata
Metadata
Assignees
Labels
No labels