edit-article

Article Description: ] by Don Sagrott, founder @sospep.com - a (short) list of commonly used terms in git land, each with a brief description to give you just a bit of a taste of what they mean before we dig into them more deeply

Chapter ID/Name:

Status: Write Writing Written

Add Photo:

Owner ID:

Content: use HTML Edit Content <h1 style="text-align: center;">TERMS</h1> <h2>[WHAT]</h2> <ol> <li>]&nbsp;the following is a (short) list of commonly used terms in git land,</li> <li>] each with a brief description to give you just a bit of a taste of what they mean before we dig into them more deeply</li> </ol> <h2>[WHY]</h2> <ol> <li>]&nbsp;understanding git</li> <li>] using git effectively</li> </ol> <h2>[WHERE]</h2> <ol> <li>]</li> </ol> <h2>[WHEN]</h2> <ol> <li>]</li> </ol> <h2>[EXAMPLE]</h2> <ol> <li>] <strong>git</strong></li> <ol> <li>] a sw program for managing source code, git is a distributed, source code mangement(SCM) (aka&nbsp;a decentralized SCM system)</li> </ol> <li>] <strong>github.com</strong></li> <ol> <li>] a source code repository hosting website, popular, free for oss projects</li> <li>] ALTS = bitbucket, ....</li> </ol> <li>] <strong>git gui</strong> -</li> <ol> <li>] a graphical user interface for executing git commands, although many have tried, none have really succeeded</li> </ol> <li><strong>] git bash</strong> -</li> <ol> <li>] a command line shell for executing git commands</li> </ol> <li><strong>] repository (aka repo) -</strong></li> <ol> <li>] a collection of source code</li> <li>] can contain many&nbsp;branches &nbsp;</li> </ol> <li><strong>] clone </strong></li> <ol> <li>] clone a repo, make an exact copy of an existing repository, usually from a repo hosting server to your local machine</li> </ol> <li><strong>] remote </strong></li> <ol> <li>]</li> </ol> <li><strong>] origin</strong></li> <ol> <li>] typically refers to the source repo</li> </ol> <li><strong>] working directory -</strong></li> <ol> <li>] refers to the local directory, git commands are typically executed from within your local working directory, using the git bash</li> </ol> <li><strong>] master</strong></li> <ol> <li>] the default 'starting' branch for any projects</li> </ol> <li><strong>] branch -</strong></li> <ol> <li>] a seperate version of the project files, use branches&nbsp;to make changes to source code (add features, fix problems)&nbsp;</li> </ol> <li><strong>] git init</strong></li> <ol> <li>] initiate the specifed directory as a git repository</li> </ol> <li><strong>] git add</strong></li> <ol> <li>] add files to the current repo</li> </ol> <li><strong>] git commit - </strong></li> <ol> <li>] create a snapshot of your "project" at a given point in time</li> </ol> <li><strong>] git push</strong></li> <ol> <li>] send/synch your changes to the specified repo&nbsp;</li> </ol> <li><strong>] git checkout -</strong><ol> <li>] git command used to set which branch of a repo you(git) is currently working with &nbsp;</li> </ol></li> <li><strong>] merge -</strong></li> <ol> <li>] including the changes from 1 branch into another branch</li> </ol> <li><strong>] rebase -</strong></li> <ol> <li>] after making changes to your local instance of a project, use rebase to pull down&nbsp;all changes submitted by other developers, since you cloned your branch,</li> </ol> <li><strong>] github pull request</strong></li> <ol> <li>] project developers can make a pull request for the project owner, where the project owner will merge the developers branch w/feature/fix into the develop or master branches</li> </ol> <li><strong>] github&nbsp;issue -</strong></li> <ol> <li>] project contributors can submit FIXES, or FEATURE REQUESTS via githubs issues feature</li> </ol> <li><strong>] git fast forward</strong></li> <ol> <li>] ....</li> </ol> <li><strong>] tags</strong></li> <ol> <li>]</li> </ol> <li><strong>] releases</strong></li> <ol> <li>] &nbsp;</li> </ol> <li><strong>] fork</strong></li> <ol> <li>] make an exact copy of an existing software project (repo) on a remote repository host, typically to use as a base/foundation to create a variant of the same sw pkg with your own modifications.</li> </ol></ol> <h2>[HOW-TO]</h2> <ol> <li>] git</li> <ol> <li>] <span style="text-decoration: underline;">install</span>, ] <span style="text-decoration: underline;">configure</span>, ]</li> </ol> <li>] github</li> <ol> <li>] register, ] create a repo, ] create an issue, ]</li> </ol> <li>] git clone</li> <ol> <li>] EXAMPLE= "git clone <a href="https://sospep.github/guide.git">https://sospep.github/guide.git</a>"</li> </ol></ol> <h2>[REFERENCE]</h2> <ol> <li><strong>] BOOK - <a href="/view/chapters?id=263" target="_blank">git started</a></strong></li> <ol> <li>] #&nbsp;2459 - <a href="/view/article?id=2459" target="_blank">table of contents</a> - a guide to learning git for noobs</li> </ol></ol>