Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDylan Taylor <dylan@dylanmtaylor.com>2021-05-15 13:09:30 -0400
committerDylan Taylor <dylan@dylanmtaylor.com>2021-05-15 13:14:54 -0400
commitdd340b9cbae197ca4f4c41c3006c4ec2858727fa (patch)
tree57711dc94d6131b6bc51f644ea99aeccfb034018
parent67b4d5d551d1e2d1e8937cc443bc58d68a439782 (diff)
Revert "Replace <br> in markdown with new line"
This reverts commit 55931a98fbd98f77addff7ebf9476a2e0c459ea5.
-rw-r--r--CONTRIBUTING.md12
1 files changed, 4 insertions, 8 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 953ac2cb..1d490a44 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -20,15 +20,13 @@ to the version it will become on release *(Patches to `v2.1.4` will be done on b
## Discussions
Currently, questions, bugs and suggestions should be reported
-through [GitHub issue tracker](https://github.com/archlinux/archinstall/issues).
-
+through [GitHub issue tracker](https://github.com/archlinux/archinstall/issues).<br>
For less formal discussions there are also a [archinstall Discord server](https://discord.gg/cqXU88y).
## Coding convention
Archinstall's goal is to follow [PEP8](https://www.python.org/dev/peps/pep-0008/) as best as it can with some minor
-exceptions.
-
+exceptions.<br>
The exceptions to PEP8 are:
* Archinstall uses [tabs instead of spaces](https://www.python.org/dev/peps/pep-0008/#tabs-or-spaces) simply to make it
@@ -43,15 +41,13 @@ The exceptions to PEP8 are:
creating formatted strings, double-quoted strings are *preferred* but not required on the outer edges *(
Example: `f"Welcome {name}"` rather than `f'Welcome {name}'`)*.
-Most of these style guidelines have been put into place after the fact *(in an attempt to clean up the code)*.
-
+Most of these style guidelines have been put into place after the fact *(in an attempt to clean up the code)*.<br>
There might therefore be older code which does not follow the coding convention and the code is subject to change.
## Submitting Changes
Archinstall uses Github's pull-request workflow and all contributions in terms of code should be done through pull
-requests.
-
+requests.<br>
Anyone interested in archinstall may review your code. One of the core developers will merge your pull request when they
think it is ready. For every pull request, we aim to promptly either merge it or say why it is not yet ready; if you go