diff options
author | Michael Czigler <37268479+mcpcpc@users.noreply.github.com> | 2021-03-19 17:15:23 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-03-19 17:15:23 -0400 |
commit | 9e7a45467cb445bf70ff2ee5973c1a2ae9717b12 (patch) | |
tree | a4e4091ce420b603cbe2fe25a57b9a5f103f36c6 /.github/CONTRIBUTING | |
parent | released at 0.2.4 (diff) | |
download | kirc-9e7a45467cb445bf70ff2ee5973c1a2ae9717b12.tar.gz kirc-9e7a45467cb445bf70ff2ee5973c1a2ae9717b12.tar.bz2 kirc-9e7a45467cb445bf70ff2ee5973c1a2ae9717b12.tar.xz kirc-9e7a45467cb445bf70ff2ee5973c1a2ae9717b12.tar.zst kirc-9e7a45467cb445bf70ff2ee5973c1a2ae9717b12.zip |
released at 0.2.5
Diffstat (limited to '')
-rw-r--r-- | .github/CONTRIBUTING | 21 |
1 files changed, 0 insertions, 21 deletions
diff --git a/.github/CONTRIBUTING b/.github/CONTRIBUTING deleted file mode 100644 index e9d9f41..0000000 --- a/.github/CONTRIBUTING +++ /dev/null @@ -1,21 +0,0 @@ -CONTRIBUTING ------------- - -Want to contribute? Great! First, read this page. - -Code reviews: -- All submissions, including submissions by project members, require review. We - use Github pull requests for this purpose. - -Some tips for good pull requests: -- Use our code - When in doubt, try to stay true to the existing code of the project. -- Write a descriptive commit message. What problem are you solving and what - are the consequences? Where and what did you test? Some good tips: - [here](http://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message) - and [here](https://www.kernel.org/doc/Documentation/SubmittingPatches). -- If your PR consists of multiple commits which are successive improvements / - fixes to your first commit, consider squashing them into a single commit - (`git rebase -i`) such that your PR is a single commit on top of the current - HEAD. This make reviewing the code so much easier, and our history more - readable. |