summaryrefslogtreecommitdiff
path: root/.github/CONTRIBUTING.md
diff options
context:
space:
mode:
authorTim Hämisch <haemtim@gmail.com>2025-06-13 17:49:49 +0200
committerGitHub <noreply@github.com>2025-06-13 17:49:49 +0200
commit5fb727a4c8d9e89acc63a1c353202423bc7b120e (patch)
tree28839211a383025df53168993d090cdccaa9bf7a /.github/CONTRIBUTING.md
parentAdd shutdown, reboot, and logout actions to launcher (diff)
parentdocs: add contributing.md (diff)
downloadcaelestia-shell-5fb727a4c8d9e89acc63a1c353202423bc7b120e.tar.gz
caelestia-shell-5fb727a4c8d9e89acc63a1c353202423bc7b120e.tar.bz2
caelestia-shell-5fb727a4c8d9e89acc63a1c353202423bc7b120e.zip
Merge branch 'caelestia-dots:main' into betteractions
Diffstat (limited to '.github/CONTRIBUTING.md')
-rw-r--r--.github/CONTRIBUTING.md21
1 files changed, 21 insertions, 0 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
new file mode 100644
index 0000000..d0239c0
--- /dev/null
+++ b/.github/CONTRIBUTING.md
@@ -0,0 +1,21 @@
+# Contributing
+
+There are only a few rules:
+- Follow the commit convention as follows:
+ - The name of the commit should be `module: change`
+ - Try to be consistent with the module names; you can look at existing commits for the module names I use
+ - If there is more than one change, the change in the commit name should be the most impactful change
+ - Put other changes in the description
+- Format your code
+ - I use the vscode qml extension with default arguments to format the code, however you do not have to use it
+ - Just try to follow the code style of the rest of the code and ensure that there is:
+ - no trailing whitespace on any lines
+ - a single space between operators
+- No AI slop allowed
+ - AI readme/docs slop = instant block
+- PLEASE TEST YOUR PRS
+ - I can't believe I have to put this here, but please test your PRs before submitting them
+ - Your PR must not break anything currently existing, or specify in the description if it does
+- PR descriptions should be descriptive
+ - Please explain what the PR does and how to use it in your PR description
+ - Also include any breaking changes and/or side effects of the PR