- Git: Version Control for Everyone Beginner's Guide
- Table of Contents
- Git: Version Control for Everyone Beginner's Guide
- Credits
- About the Author
- Acknowledgement
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Breathe Easy – Introduction to Version Control System
- 2. Welcome Aboard – Installing Git
- 3. Polishing Your Routine – How to Increase Everyday Productivity
- Suit up – getting ready for your Git
- Initiation
- Time for action – initiation in GUI mode
- Time for action – initiation in CLI mode
- Time for action – configure Git in GUI mode
- Time for action – configure Git in CLI mode
- Adding your files to your directory
- Time for action – adding files to your directory (GUI and CLI mode)
- Time for action – usage of .gitignore
- Committing the added files
- Time for action – committing files in GUI mode
- Time for action – committing files in CLI mode
- Time for action – rescan in GUI mode
- Checking out
- Time for action – checking out using GUI mode
- Time for action – checking out using CLI mode
- Resetting
- Time for action – reset using GUI mode
- Time for action – reset using CLI mode
- Summary
- 4. Split the Load – Distributed Working with Git
- Why share your files
- Time for action – adding a remote origin using CLI mode
- Time for action – resume your work from anywhere using CLI mode
- Time for action – adding a remote origin using GUI mode
- Time for action – resume your work from anywhere using GUI mode
- Time for action – creating a bare repository in CLI mode
- Time for action – creating a bare repository in GUI mode
- Summary
- 5. Be a Puppet Master – Learn Fancy Features to Control Git's Functions
- Why learn such fancy features
- Time for action – getting acquainted with shortlog
- Time for action – parameterizing shortlog
- Time for action – skip commit logs
- Time for action – filter logs with date range
- Time for action – searching for a word/character match
- Time for action – emulate the mess
- Time for action – clean up your mess with pattern match
- Time for action – wipe out your mess completely, no exceptions
- Time for action – lightweight/unannotated tagging
- Time for action – referencing tags
- Time for action – annotated tagging
- Summary
- 6. Unleash the Beast – Git on Text-based Files
- Git for text-based files – an introduction
- Multiplayer mode – multiple players at a time
- Time for action – getting ready to share
- Time for action – distributed work force
- Time for action – Bob's changes
- Time for action – Lisa's changes
- Time for action – Lisa examines the merge conflict
- Time for action – Lisa resolves the merge conflict
- Time for action – team members get sync with the central bare repo
- Summary
- 7. Parallel Dimensions – Branching with Git
- What is branching
- Why do you need a branch
- When do you need a branch
- Practice makes perfect: branching with Git
- Time for action – creating branches in GUI mode
- Time for action – creating branches in CLI mode
- .config file – play with shortcuts
- Time for action – adding simple aliases using CLI
- Time for action – chain commands with a single alias using CLI
- Time for action – adding complex aliases using GUI
- Summary
- 8. Behind the Scenes – Basis of Git Basics
- Index
When the tag command is executed, Git performs the following steps:
- Gets the SHA-1 ID of the referred commit.
- Validates the given tag name with the existing tag names.
- If it's a new name, it validates the name with the naming conventions.
- If the name abides by the rules, a tag object gets created with the given name mapped to the acquired SHA-1 ID, which is found inside
.git/refs/tags/.
The following figure shows the association of the tag object along with other objects:
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.