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

Trying to fix my mistakes ...

Browse source
This commit is contained in:
parulin 2025-08-16 14:28:31 -04:00
parent e3e699fa5e
commit 5281f045dc
No known key found for this signature in database
GPG key ID: 65099A5B0E31336C
10 changed files with 300 additions and 1527 deletions
Download patch file Download diff file Expand all files Collapse all files

1
developer/code/code-signing.rst
View file

@ -111,6 +111,7 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
3. (Optional) Create signed tags. Signed commits are totally sufficient to contribute to Qubes OS. However, if you have commits which are not signed and you do not want to change them, you can create a signed tag for the commit and push it before the check.
This is useful for example, if you have a commit back in the git history which you like to sign now without rewriting the history.
.. code:: console

1
developer/code/source-code.rst
View file

@ -61,6 +61,7 @@ How to Send Patches
If you want to :ref:`contribute code <introduction/contributing:contributing code>` to the project, there are two ways. Whichever method you choose, you must :doc:`sign your code </developer/code/code-signing>` before it can be accepted.
- **Preferred**: Use GitHub’s `fork & pull requests <https://guides.github.com/activities/forking/>`__.
Opening a pull request on GitHub greatly eases the code review and tracking process. In addition, especially for bigger changes, it’s a good idea to send a message to the :ref:`qubes-devel mailing list <introduction/support:qubes-devel>` in order to notify people who do not receive GitHub notifications.
- Send a patch to the :ref:`qubes-devel mailing list <introduction/support:qubes-devel>` (``git format-patch``).