LNCD

Table of Contents

  • LNCD Home
  • Administration
  • Notebooks
  • Journal Club Presentations
  • Publications
  • Current Projects
  • Completed Projects
  • Current Grants
  • Datasets by Project
  • Brain ROIs and Measures
  • ️Tools And Methods
  • Big Data
  • RA Homepage
  • Undergrad Resources
  • Recent Changes
  • Maintenance
  • Site Map
  • Random Page
LNCD
Admin » Github setup

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
tools:github [2026/06/17 14:00] – [Authentication] willtools:github [2026/06/17 14:13] (current) – [Github setup] will
Line 1: Line 1:
 ====== Github setup ====== ====== Github setup ======
-Github (source forge) is not git (local-first distributed source control management software)! See [[:tools:git]] for using ''git''.+Github (the source forge) speaks but is not ''git'' (the local-first distributed source control management software)! See [[:tools:git]] for using the ''git'' command line tool.
  
 See [[:tools:zenodo]] for creating a DOI for your code hosted on Github.com. See [[:tools:zenodo]] for creating a DOI for your code hosted on Github.com.
Line 7: Line 7:
 Github setup includes Github setup includes
   - [[#new_repo|creating]] or [[#existing_repo|finding]] an existing remote github repository url   - [[#new_repo|creating]] or [[#existing_repo|finding]] an existing remote github repository url
-    * use **ssh** url like ''git@github.com:group/repo'' ( instead of ''%%https://github.com/group/repo%%'') +    * use **ssh** url like ''git@github.com:group/repo'' (instead of ''%%https://github.com/group/repo%%'')
     * avoid conflicting histories: <wrap important>dont generate a readme when creating a new repo</wrap>      * avoid conflicting histories: <wrap important>dont generate a readme when creating a new repo</wrap> 
   - syncing that with your files (on your computer, on rhea, on PSC, etc)   - syncing that with your files (on your computer, on rhea, on PSC, etc)
     * <wrap tip> be sure you ''cd'' to the right directory before running ''git'' commands</wrap>     * <wrap tip> be sure you ''cd'' to the right directory before running ''git'' commands</wrap>
-  - [[#ssh_keys|authenticating]] with github for ''git push'' permissions. +  - [[#ssh_keys|authenticating]] with github for ''git push'' permissions. See [[https://docs.github.com/en/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys|connecting-to-github-with-ssh]]
     * <wrap tip>ssh keys recommended</wrap>     * <wrap tip>ssh keys recommended</wrap>
     * <wrap alert> ''ssh-keygen'' only once per user@server. don't run if existing ''~/.ssh/id*.pub''</wrap>     * <wrap alert> ''ssh-keygen'' only once per user@server. don't run if existing ''~/.ssh/id*.pub''</wrap>
Line 18: Line 18:
  
 <WRAP alert> <WRAP alert>
-If you have an existing directory you want to put on github, **DO NOT** generate a readme when creating the  github repository.+If you have an existing directory you want to put on github, **DO NOT** generate a readme when creating the  github repository. Instead, use the [[#existing_repo|Existing Repo section]] below instead.
 </WRAP> </WRAP>
    
Line 29: Line 29:
  
 ===== Existing Repo ===== ===== Existing Repo =====
 +
 +To get existing code onto your local workstation or server environment, run ''git clone'' to create a new local directory with the remote code.
  
   * Copy the ssh url of your new repository. Green ''<> Code'' button > ''Local'' Tab > ''SSH'' header.   * Copy the ssh url of your new repository. Green ''<> Code'' button > ''Local'' Tab > ''SSH'' header.