GitHub

GitHub is a web-based platform that provides hosting of coding repositories. It offers a centralized location for people to store, manage, and allow collaboration on their code. It is especially useful for version control and project tracking. The following information is geared towards linking gluey annex repositories with GitHub, but can easily be used to link your home computer to a GitHub repository. This wiki page is being updated as the author learns how to use GitHub, so if you know a better, more efficient way to accomplish a task then by all means please do it that way (... and add an addendum to this page if you have a login).

The Setup


Sign up for a GitHub account by going to the GitHub website and create a new account - If you do not make your email address public you will have problems pushing your code later

Once you're logged in, click on the "+" sign at the top-right corner of the GitHub homepage and select "New repository" to create a new repository. Give your repository a name and provide a description.  The repository name will be your folder name on gluey (see below) Repository description is optional Repository Setting:  Private vs. Public License (optional) - MIT License is well known and least restrictive</li> You can add a README file</li> You can also rename the main branch (this must be done before the repository is created, changing the name will change all subsequent repositories that are made in the future)</li> And more ...</li> </ul> </ul>

Once the repository is setup online, add a Personal Access Token</li> <ul> At the top-right of the GitHub website click on the pull-down and select "Settings"</li> On the left select "Developer settings" located at the bottom </li> Then on the left select "Personal access tokens"</li> Select "Fine-grained tokens" or "Tokens (classic)", I did the prior one</li> <ul> For the Fine-grained token you will need to select which permissions you'd like to allow (not sure about the classic token)</li> Select a period for the token to be valid, upto 90 days maximum (I believe)</li> Once complete it will provide you with the token you can copy, this will be used in place of your password later</li> </ul> </ul>

Clone your repository</li> <ul> Log in to gluey using a VNC and navigate to the location in your annex where you'll be working</li> <ul> You can do the same for your home computer, you'll just need to open a terminal or command prompt and navigate to the directory where you want to store your code</li> </ul> Use the command: git clone https&#58;&#47;&#47;github&#46;com&#47;your-username&#47;your-repository&#46;git &ensp; - Make sure to replace "your-username" with your GitHub username and "your-repository" with the name of your repository</li> You will now need to login. Use your GitHub Username, but make sure to use the Personal Access Token you created earlier and  NOT  your GitHub password</li> </ul>

<li>At this point you should have a new folder in your annex with the name of your GitHub repository</li> <ul> <li>Confirm that the remote repository is correctly added, use the command: git remote -v </li> <li>If needed, you can link the local repository to the remote repository using: git remote add origin repository-url </li> </ul>

<li>To switch to or determine a branch in Git, you can use the git checkout command: <ul> <li>Determine the name of the branch you want to switch to via: git branch &ensp; - It will show all branches available and indicate your current branch with a *  </li> <li>Create a new branch using: git branch new-branch-name </li> <li>Switch to that branch and work in it via: git checkout new-branch-name </li> <li>The two steps above can be combined: git checkout -b new-branch-name &ensp; - This will create and switch to the new branch in one step</li> </ul>

<li>Add files/folders to your directory</li>

<li>When you're ready to save, make sure you are in the root directory of your repository or the directory where the new folder you want to save is located. Then use the git add command to add the new folder and its contents to      the staging area. Run the following command: git add folder-name &ensp;- Adds the specified file or folder &emsp; OR   git add . &ensp;- Adds all new files and folders in the current directory recursively, does not add higher directory information &emsp; OR   git add -A ''&ensp;- Adds all files: new, modified, and deleted files. It will include files in the current directory and in higher directories that belong to the same git repository'' &emsp; OR   git add -u ''&ensp;- Adds modified and deleted files only. Excludes new files. It will include files in the current directory and in higher directories that belong to the same git repository'' For a more detailed description of git add go to: https://github.com/git-guides/git-add</li>

<li>Once the new folder/file is added to the staging area, you can commit the changes using the git commit command: git commit -m "Commit message" ''&ensp; - Replace Commit message with a descriptive message summarizing the changes you made. Keep " " around your message''</li>

<li>After committing the changes (on your local machine), you can push them to the remote repository on GitHub using the git push command: git push origin branch-name &ensp; - Replace branch-name with the name of the branch you want to push to (e.g., main) &ensp; - You will need to login with your Username and Personal Access Token</li> </ol>

The Extras
<ul>

<li>git status &ensp; - This command shows the branch you're on, what files are in the working or staging directory, and other important information &emsp; Example : mcintyre@gluey/nfs/direct/annex/mcintyre/GitRepo/Radphi_pi02gp/RUN0 $ git status # On branch PI0 # Untracked files: #  (use &quot;git add &lt;file&gt;...&quot; to include in what will be committed) #       #	STEP6/ #	STEP7/ nothing added to commit but untracked files present (use &quot;git add&quot; to track) </li>

<li>git reset &ensp; - This command unstages all changes (e.g. all git add performed before a git commit) </li> <li>git reset file-name &ensp; - This command undoes git add for uncommited changes to file file-name </li>