Editing CommunityData:Git (section)

== Gitea ==

We have a private git server which uses [https://about.gitea.com/ gitea] to manage permissions for git repositories. It's like a private Github server that hosts our respositories, but just ours, and on our server. If you have a question about Gitea, please message cdsc-it or look in [https://docs.gitea.com/ Gitea's general documentation]. 

===Making an Account/SSH Keys===

You can make a new Gitea account on [https://gitea.communitydata.science/user/sign_up this webpage] using your email address and password. Connect your local git to your new Gitea account by adding your SSH key ((usually ~/.ssh/id_rsa.pub) to "SSH/GPG Keys" in your user "Settings" page.

===Cloning a repository===

"Cloning" a repository downloads the files, as well as the history, of a repository. It also creates a new git instance in that directory, so that you can commit changes to the code.

To clone a repository, run the following command: 

  gitea@gitea.communitydata.science:$USERNAME/REPOSITORY_NAME$.git

===Creating a new repository===

To create a new Gitea repository, follow the instructions in the ``Create'' button in the top-left corner of the homepage, immediately left of the user profile icon.

===Pushing data into a new repository on the server from a local git repository you already have===

You could then go to wherever the files are that you would like to track, and add this repository as a remote, like so:
<source lang='bash'>
$ cd foo
$ git remote add origin gitea@gitea.communitydata.science:$USERNAME/REPOSITORY_NAME$.git
$ git push --set-upstream origin main
</source>

If this project already exists in git, then it's even easier. Just change the remote, and push it.

<source lang='bash'>
$ git remote set-url origin gitea@gitea.communitydata.science:$USERNAME/REPOSITORY_NAME$.git
$ git push
</source>

====Adding new users to repository====

To add new users, use the project Settings page from the home page of the repository.

===Setting the default branch===

Gitea sometimes has issues because it expects the default branch to be "main", but some repositories may have a different default branch name. To fix this (if it is a problem), change the default branch for the repositories under "Settings > Branches".