581
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + Line 102:
Line 104: − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 131:
Line 247: − <li><u>Adding a repository from your local computer to GitHub</u><br>+ −   1) On your local computer, initialize the folder you want to adds as a repository:<br> −     - Use <b>cd</b> to navigate to the folder that contains the work you'd like to track/backup<br> −     - Type <b>git init</b> to initialize the folder for Git tracking<br> −     - Type <b>touch .gitignore</b> to create a blank file in that folder, which can later be modify to specify files or types of files you don't want to track (<i>optional step</i>)<br><br> − −   2) Go to https://github.com/ , login, and create a repository as described above. Name the repository the same as your working folder you did the git init command in<br><br> − −   3) On your local computer link your working folder to the GitHub repsoitory:<br> −     - Type <b>git remote add origin <i>github-repository-url</i></b><br> −         <i>github-repository-url</i> can be found online. In your repository folder click on the green [<> Code] button then under the Local tab you'll see Clone HTTPS. Click the copy button to paste the − address into the line of code above<br><br> − −   4) On your local computer, merge the two repositories (local and online):<br> −     - Type <b>git pull origin main</b><br> −         This assumes the GitHub branch is named <i>main</i> in the repository you created online<br><br> − − −   5) On your local computer, add files to track:<br> −     - Type <b>git add .</b><br><br> − −   6) On your local computer, commit that add:<br> −     - Type <b>git commit -m "Message here"</b><br> −         Change <i>Message here</i> to a brief description of the reason for the commit (ex: Initial commit). Make sure to keep ""<br><br> − −   7) On your local computer, change (if required) the branch name to the name listed in the online repository:<br> −     - Typing <b>git branch</b> tells you the name(s) of the branch(es) with the current one having a * next to it<br> −     - If you need to modify your local computer's branch name use <b>git branch -M main</b> where <i>main</i> is the name to change the branch to<br> −     - Use <b>git branch</b> to verify the change<br><br> − −   8) On your local computer, push your commit:<br> −     - Type <b>git push -u origin main</b><br> −         You'll need to enter your GitHub profile name and your Personal Access Token to complete the push<br><br> −     - The purpose of the <i>-u</i> flag is to establish an upstream relationship between the local branch and the specified remote branch<br> −   This is typically done on the initial push to a remote repository. After that, you don't need to use the -u flag again for subsequent pushes to the same branch<br><br> − −   9) At this point your online GitHub repository should be the same as the working folder on your local computer.<br> −   You can now continue to code and push/pull to GitHub as needed to track/update changes. Good luck, if it doesn't work don't blame me ... I only work here :) <br>
→Setup Option #2 (Local computer → GitHub)
<font size="3">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).</font>
<font size="3">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).</font>
== <u><i>The Setup</i></u> ==
== <i>Setup Option #1 (GitHub → local computer)</i> ==
Adding a repository in your GitHub account to your local computer (e.g. cloning).
<ol>
<ol>
<!-- Step 1 -->
<!-- Step 1 -->
</ol>
</ol>
== <u><i>The Extras</i></u> ==
== <i>Setup Option #2 (Local computer → GitHub)</i> ==
Adding a repository from your local computer to GitHub
<ol>
<!-- Step 1 -->
<li>On your local computer, initialize the folder you want to adds as a repository:<br>
  - Use <b>cd</b> to navigate to the folder that contains the work you'd like to track/backup<br>
  - Type <b>git init</b> to initialize the folder for Git tracking<br>
  - (<i>optional step</i>) Type <b>touch .gitignore</b> to create a blank file in that folder, which can later be modify to specify files or types of files you don't want to track </li><br>
<!-- Step 2 -->
<li>Go to https://github.com/ , login, and create a repository as described above. Name the repository the same as your working folder you did the git init command in</li><br>
<!-- Step 3 -->
<li>On your local computer, link your working folder to the GitHub repsoitory:<br>
  - Type <b>git remote add origin <i>github-repository-url</i></b><br>
    <i>github-repository-url</i> can be found online: <br>
        - In your repository folder click on the green [<> Code] button then under the Local tab you'll see Clone HTTPS <br>
        - Click the copy button to paste the address into the line of code above</li><br>
<!-- Step 4 -->
<li>On your local computer, merge the two repositories (local and online):<br>
  - Type <b>git pull origin main</b><br>
    This assumes the GitHub branch is named <i>main</i> in the repository you created online </li><br>
<!-- Step 5 -->
<li>On your local computer, add files to track:<br>
<b>git add <i>folder-name</i></b><br>
  <i> - Adds the specified file or folder</i><br>
  OR <br>
<b>git add .</b> <br>
  <i> - Adds all new files and folders in the current directory recursively, does not add higher directory information</i><br>
  OR <br>
<b>git add -A</b> <br>
  <i> - 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</i><br>
  OR <br>
<b>git add -u</b> <br>
  <i> - 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</i><br><br>
For a more detailed description of <i>git add</i> go to: https://github.com/git-guides/git-add</li><br>
<!-- Step 6 -->
<li>On your local computer, commit that add:<br>
  - Type <b>git commit -m "Message here"</b><br>
    Change <i>Message here</i> to a brief description of the reason for the commit (ex: Initial commit) <br>
    Make sure to keep "" </li><br>
<!-- Step 7 -->
<li>On your local computer, change (if required) the branch name to the name listed in the online repository:<br>
  - Typing <b>git branch</b> tells you the name(s) of the branch(es) with the current one having a * next to it<br>
  - If you need to modify your local computer's branch name use <b>git branch -M main</b> where <i>main</i> is the name to change the branch to<br>
  - Use <b>git branch</b> to verify the change </li><br>
<!-- Step 8 -->
<li>On your local computer, push your commit:<br>
  - Type <b>git push -u origin main</b><br>
    You'll need to enter your GitHub profile name and your Personal Access Token to complete the push<br><br>
  - The purpose of the <i>-u</i> flag is to establish an upstream relationship between the local branch and the specified remote branch<br>
This is typically done on the initial push to a remote repository. After that, you don't need to use the -u flag again for subsequent pushes to the same branch </li><br>
<!-- Step 9 -->
<li>At this point your online GitHub repository should be the same as the working folder on your local computer <br>
  You can now continue to code and push/pull to GitHub as needed to track/update changes. Good luck, if it doesn't work don't blame me ... I only work here :) </li><br>
</ol>
== <i>Ignoring Files (.gitignore)</i> ==
There are various reasons to not want to track/push files. The following situation helps when you're having trouble pushing files due to them being too big (>50 MB, GitHub max) .
<ol>
<li><u>Find those problem files</u>: <br>
  - Ensure you're in the directory of interest (use <b>cd </b> command as needed) <br>
  - Type <b>find . -type f -size +50M </b><br>
  - This will list files that are above GitHub's 50 MB limit </li><br>
<li><u>Create a .gitignore file</u>: <br>
  - To create one use the command <b>touch .gitnore </b><br>
    Make sure you are in the root folder of your repository on your local computer when you use this command <br>
    <u>Hint</u> - The root folder is named the same as your repository on GitHub </li><br>
<li><u>Use your favorite text editor to open the file (i.e. Vim, Notepad++, etc.)</u>: <br>
  - Enter the oversized files from above into the girignore file<br>
    Make sure to remove the <b>.</b> if you decide to copy/paste <br>
<i><u>Example</u>:</i></li>
<!-- Example -->
<pre># Remember: A line that follows # is a comment.
#
# To ignore a file update this file (.gitignore) then add, commit, and push this file.
# Do this BEFORE any other pushes so the rule will be in effect.
# These files are above GitHub's recommended file size (50 MB). SUBFOLDER/FILE
MonteCarlo/fermi.txt
Examples/mctuple.root
Examples/mctuple.hbook
Examples/ntuple.root
Examples/log
Examples/omega2p_sim_1.itape
Examples/ntuple.hbook
# These are object files. Code that is compiled to machine code, no need fo me to saved/tracked in GitHub.
# * is a wild card, so anything that has .o at the end is ignored using *.o, while *.o.* says ignore anything that has .o. within the name.
*.o
*.o.*
</pre><br>
<li><u>Ignore already checked in files</u>: <br>
  - Since you already tried and failed to fully push those file, you'll need to untrack them <br>
  - From your terminal type <b>git rm --cached FILENAME </b><br>
    Hint - You can copy/paste from the find results <b>git rm --cached /SUBFOLDER/FILENAME </b><br>
  - Do this for all files that require it before proceeding </li><br>
<li><u>Add, commit, and push the .gitignore file</u>: <br>
  - Add the gitignore file using <b>git add .gitignore </b> <br>
  - Commit the file using <b>git commit -m "Files to ignore" </b> <br>
  - Push the commit using <b>git push origin main </b> <br>
    Now subsequent pushes will know to ignore those files or types of files </li> <br>
== <u><i>Extras</i></u> ==
<ul>
<ul>
<!-- 0 -->
<!-- 0 -->
<!-- 3 -->
<!-- 3 -->
</li>
</li>