Submit patches to Gitea repositories: Difference between revisions
Created page with "The Community Data Science Collective uses Gitea which is a self-hosted system that is similar to Github. Because of spam, it is not possible for us to leave new user registration open. This page includes description on how to contribute to our Gitea repositories. There are two approaches: * #Submit a single patch — a simple way to get us a single patch * #Signup for an account — appropriate if you anticipate contributing to projects multiple times or over t..." |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
git clone [URL from summary page] | git clone [URL from summary page] | ||
The most reliable way to send a patch without an | The most reliable way to send a patch without an accounts over email. You can do that by following these steps: | ||
# Clone the repository with the command above. | # Clone the repository with the command above. | ||
| Line 19: | Line 19: | ||
If you are more comfortable putting a git repository with your changes online somewhere else and sending a link that to repository, that works too! | If you are more comfortable putting a git repository with your changes online somewhere else and sending a link that to repository, that works too! | ||
If you can't find an email or if there's no owner listed or you can't find an email address for the person (sorry!), you can just send it to collective@communitydata.science and we'll make sure it gets to the right place! | |||
== Signup for an account == | == Signup for an account == | ||
Details on how to sign up for a | Details on how to sign up for a repository on our Gitea are over on [[CommunityData:Git#Creating an account]]. | ||
Latest revision as of 17:18, 14 June 2025
The Community Data Science Collective uses Gitea which is a self-hosted system that is similar to Github. Because of spam, it is not possible for us to leave new user registration open. This page includes description on how to contribute to our Gitea repositories. There are two approaches:
- #Submit a single patch — a simple way to get us a single patch
- #Signup for an account — appropriate if you anticipate contributing to projects multiple times or over time
Submit a single patch[edit]
If you click on any repository, you will see a text box that begins with HTTPS. You can get a full copy of any public repository by running the command of the form:
git clone [URL from summary page]
The most reliable way to send a patch without an accounts over email. You can do that by following these steps:
- Clone the repository with the command above.
- Make the changes that you want to the files in the repository with your text editor, etc.
- Commit the changes locally with the command: git commit -a
- Output a patch for your commit with the command: git format-patch HEAD~1
- Attach that patch (it will be a file with a name like 001-SOMETHING.patch) to an email and send it to the owner of the repository.
If you are more comfortable putting a git repository with your changes online somewhere else and sending a link that to repository, that works too!
If you can't find an email or if there's no owner listed or you can't find an email address for the person (sorry!), you can just send it to collective@communitydata.science and we'll make sure it gets to the right place!
Signup for an account[edit]
Details on how to sign up for a repository on our Gitea are over on CommunityData:Git#Creating an account.
