awesome-zsh-plugins/Contributing.md

23 lines
1.8 KiB
Markdown
Raw Normal View History

2015-01-19 18:23:31 +00:00
# Contributing
2015-06-04 17:04:47 +00:00
First and foremost, thanks for the help, I appreciate all of the contributions, and the awesome-zsh-plugins list wouldn't be nearly as complete without them.
2015-01-19 18:23:31 +00:00
2015-06-04 17:04:47 +00:00
## To add to the list:
2015-04-03 06:02:27 +00:00
2016-05-14 03:57:18 +00:00
### Submit a pull request.
2015-06-04 17:04:47 +00:00
* Descriptions should be clear, concise, and non-promotional.
* The list is split into sections for frameworks, plugins, themes and completions, please add your entries to the appropriate sections. If an entry is a plugin that provides both plugin functionality and tab completions, add it to the plugins section. The completions section is meant for things that only provide extra tab completions.
2016-05-14 03:57:18 +00:00
* Descriptions should follow the link, on the same line, with capitalization consistent with the other entries in the section.
* Each entry should be a single line. This makes keeping the sections sorted easier. We let the GitHub formatter handle adding any required line breaks rather than embedding breaks in the lines ourselves.
* Each entry should be limited to one link, and that link should be the first part of the line. It is ok to submit more than one entry in a PR.
2015-06-04 17:04:47 +00:00
* If you're submitting a theme, please try to make sure that the theme repo has a screen shot so that list users can tell what it looks like before installing it.
* Please make sure all framework, plugin, themes or completions list entries are sorted *alphabetically*.
* The link should be named the name of the package or project.
* Your PR should pass the Travis checks. If the travis checks show an error that you didn't add (a previous plugin entry has gone 404, for example) you don't _have_ to fix those errors, though I'll appreciate the help if you do.
* It is fine to have multiple new entries in a single PR
2015-06-04 17:04:47 +00:00
## To remove an entry:
Open an issue to discuss why the entry should be removed, and optionally create a PR.