Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-05-11 03:05:20 -04:00
Code Issues Projects Releases Packages Wiki Activity

Fixed spelling and moved section how to contribute.

Browse source 
* Normal git pull-request workflow and patches are used.
This commit is contained in:
Robin Schneider 2015-07-19 18:41:14 +02:00
parent a8dddefd3f
commit e1550f6ab6
No known key found for this signature in database
GPG key ID: 489A4D5EC353C98A
2 changed files with 16 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

15
SourceCode.md
View file

@ -33,5 +33,16 @@ git clone git://github.com/QubesOS/qubes-core-admin.git core-admin
If you want to contribute to the project, there are two preferred ways:
1. Use github [fork & pull requests](https://guides.github.com/activities/forking/)
2. [sending a patch](/doc/DevelFaq/#q-how-do-i-submit-a-patch) via the project's mailing list (`git format-patch`).
1. Use github [fork & pull requests](https://guides.github.com/activities/forking/)
2. [sending a patch](/doc/DevelFaq/#q-how-do-i-submit-a-patch) via the project's mailing list (`git format-patch`).
## Sending a patch
1. Make all the changes in your working directory, i.e. edit files, move them around (you can use 'git mv' for this), etc.
2. Add the changes and commit them (git add, git commit). Never mix different changes into one commit! Write a good description of the commit. The first line should contain a short summary, and then, if you feel like more explanations are needed, enter an empty new line, and then start the long, detailed description (optional).
3. Test your changes NOW: check if RPMs build fine, etc.
4. Create the patch using 'git format-patch'. This has an advantage over 'git diff', because the former will also include your commit message, your name and email, so that \*your\* name will be used as a commit's author.
5. Send your patch to qubes-devel. Start the message subject with the '[PATCH]' string.