From 9e7a45467cb445bf70ff2ee5973c1a2ae9717b12 Mon Sep 17 00:00:00 2001
From: Michael Czigler <37268479+mcpcpc@users.noreply.github.com>
Date: Fri, 19 Mar 2021 17:15:23 -0400
Subject: released at 0.2.5

---
 .github/CONTRIBUTING | 21 ---------------------
 1 file changed, 21 deletions(-)
 delete mode 100644 .github/CONTRIBUTING

(limited to '.github/CONTRIBUTING')

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.
-- 
cgit v1.2.3