Git-Mirrors/Qubes-Community-Content
1
0
Fork 0
mirror of https://github.com/Qubes-Community/Contents.git synced 2025-01-08 13:57:58 -05:00
Code Issues Packages Projects Releases Wiki Activity

mention self-labelling issue

Browse Source
This commit is contained in:
awokd 2018-03-17 09:37:47 +00:00 committed by GitHub
parent c398d6d6ce
commit a78e678917
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/no-git-submissions.md
View File

@ -2,7 +2,8 @@
Contributing to the official Qubes OS [documentation](https://www.qubes-os.org/doc/) requires contributors to understand git concepts like forking a repository, submitting pull requests and keeping a forked repository synchronized with upstream. Some of those concepts are easy to master, others are more involved.
Qubes users who don't want to learn git for a reason or another - or who don't feel confident submitting a pull request (PR) - can simply create an issue in this github community page in the "Issues" tab above with any content they see fit: addition or improvements to documentation, suggestions, tips, typo fixes, one-liners, ...
Qubes users who don't want to learn git for a reason or another - or who don't feel confident submitting a pull request (PR) - can simply create an issue in this github community page in the "Issues" tab above with any content they see fit: addition or improvements to documentation, suggestions, tips, typo fixes, one-liners, etc.
Please add the `doc-contrib` label/tag to your issue if you would like to submit this document.
After (optional) discussion in the issue's thread and if the content is deemed fit for submission (whether to this project's unoffical documentation repository or to Qubes' official qubes-doc repository) a community member will create a git pull request on your behalf and take care of anything "git", or alternatively he will guide you in creating your own PR - if you'd like to of course. Note however that in the former case you'll loose attribution/credit because github doesn't allow transferring a pull request's ownership.