Git glossary - RedHatInsights/red-hat-ansible-automation-platform-documentation GitHub Wiki

The repository of record for the documentation: https://github.com/RedHatInsights/red-hat-ansible-automation-platform-documentation

Your copy, or fork, of the upstream repository on your GitHub instance, created by forking the upstream repository.

Create a copy of the upstream repository on your GitHub instance.

Copy your fork of the repository to your local file system.

When you are working in your cloned local copy of the repository, the location of the repository on GitHub are called remotes. The repository that you clone from is tagged ‘origin’ by default. Configure the upstream repository as a remote; call it upstream.

Branch created for doing work. These are usually created from an upstream branch. You can either create the branch locally, or you can create it in your fork on GitHub and pull it to your local machine.

Acts as a pointer to the commit you have checked out. When you checkout a branch, git automatically checks out the newest commit in the branch, so HEAD points to the tip of the branch. HEAD is actually a file: the contents indicate whether you have checked out a branch or an individual commit.

Indicates that you have checked out a commit, not a branch. When you are squashing commits or resolving merge conflicts, Git enters a detached head state until you have finished the work.

You can’t edit the upstream repository. Instead, you must make a request to upstream to pull in the changes that you made in a topic branch in your fork (origin). Create the pull request on the GitHub UI, making sure to add a descriptive message.