X-Git-Url: https://git.madduck.net/etc/vim.git/blobdiff_plain/3091fc902f2ab3509e534a9acb3db3a184adb785..9762221d9cf8455ddbd79c1f3c3580c2934ec800:/.vim/bundle/vim-pathogen/CONTRIBUTING.markdown?ds=sidebyside

diff --git a/.vim/bundle/vim-pathogen/CONTRIBUTING.markdown b/.vim/bundle/vim-pathogen/CONTRIBUTING.markdown
new file mode 100644
index 00000000..3bbabf8d
--- /dev/null
+++ b/.vim/bundle/vim-pathogen/CONTRIBUTING.markdown
@@ -0,0 +1,18 @@
+Follow the commit message guidelines at [commit.style](https://commit.style).
+This is an absolute requirement for my repositories, and doing so proves you
+actually read the contribution guidelines, which makes for a good first
+impression.
+
+Good commit messages imply good commits.  Pull requests should typically be a
+single commit, or for the rare complicated case, a series of atomic commits.
+If I request a change, use `git commit --amend` or `git rebase --interactive`
+and force push to your branch.
+
+For feature requests, don't be shy about proposing it in an issue before
+drafting a patch.  If it's a great idea, I might do it for you.  If it's a
+terrible idea, no patch will change my mind.
+
+The worst ideas are configuration options.  You'll need to provide a great
+justification in order to persuade me to take on the maintenance and support
+burden it will inevitably entail.  See if you can get away with a custom map
+or autocommand instead.