gapodo
/
forgejo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[DOCS] accept patches via email 

Fixes: https://codeberg.org/forgejo/meta/issues/53

Signed-off-by: Loïc Dachary <loic@dachary.org>
forgejo-development
Loïc Dachary 2022-11-28 18:19:44 +01:00 committed by Gitea
parent e302cf89d8
commit 6120fcac5e
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
CONTRIBUTING/WORKFLOW.md
View File

@ -77,3 +77,10 @@ Returning contributors can figure out which *Feature branch* to base their pull
*Feature branches* can contain a number of commits grouped together, for instance for branding the documentation, the landing page and the footer. It makes it convenient for people working on that topic to get the big picture without browsing multiple branches. Creating a new *Feature branch* for each individual commit, while possible, is likely to be difficult to work with. *Feature branches* can contain a number of commits grouped together, for instance for branding the documentation, the landing page and the footer. It makes it convenient for people working on that topic to get the big picture without browsing multiple branches. Creating a new *Feature branch* for each individual commit, while possible, is likely to be difficult to work with.
Observing the granularity of the existing *Feature branches* is the best way to figure out what works and what does not. It requires adjustments from time to time depending on the number of contributors and the complexity of the Forgejo codebase that sits on top of Gitea. Observing the granularity of the existing *Feature branches* is the best way to figure out what works and what does not. It requires adjustments from time to time depending on the number of contributors and the complexity of the Forgejo codebase that sits on top of Gitea.
## Mail based patches
It is not required to have an account on Codeberg to contribute to Forgejo. Patches are accepted and reviewed via email at patch@forgejo.org. For more information see [email + git = <3](https://git-send-email.io/).
Upon reception, the patch will be used to open a pull request for discussion. The link to the pull request will be sent back, to allow reading eventual comments. The comments can be addressed by sending other patches by email.