Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also .

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also .
  • 1 commit
  • 1 file changed
  • 0 commit comments
  • 1 contributor
Commits on Sep 22, 2018
Showing with 12 additions and 6 deletions.
  1. +12 −6 CONTRIBUTING.md
View
@@ -1,17 +1,23 @@
# Contributing
All projects under the Pylons Project, including this one, follow the guidelines established at [How to Contribute](https://pylonsproject.org/community-how-to-contribute.html) and [Coding Style and Standards](https://pylonsproject.org/community-coding-style-standards.html).
All projects under the Pylons Project, including this one, follow the guidelines established at [How to Contribute](https://pylonsproject.org/community-how-to-contribute.html), [Coding Style and Standards](https://pylonsproject.org/community-coding-style-standards.html), and [Pylons Project Documentation Style Guide](https://docs.pylonsproject.org/projects/docs-style-guide/).
You can contribute to this project in several ways.
- [File an Issue on GitHub](https://github.com/Pylons/pyramid-cookiecutter-starter/issues)
- Fork this project and create a branch with your suggested change. When ready, submit a pull request for consideration. [GitHub Flow](https://guides.github.com/introduction/flow/index.html) describes the workflow process and why it's a good practice. When submitting a pull request, sign [CONTRIBUTORS.txt](https://github.com/Pylons/pyramid-cookiecutter-starter/blob/master/CONTRIBUTORS.txt) if you have not yet done so.
- Join the IRC channel [#pyramid](https://webchat.freenode.net/?channels=pyramid) on irc.freenode.net.
* [File an Issue on GitHub](https://github.com/Pylons/pyramid-cookiecutter-starter/issues).
* Fork this project, create a new branch, commit your suggested change, and push to your fork on GitHub.
When ready, submit a pull request for consideration.
[GitHub Flow](https://guides.github.com/introduction/flow/index.html) describes the workflow process and why it's a good practice.
When submitting a pull request, sign [CONTRIBUTORS.txt](https://github.com/Pylons/pyramid-cookiecutter-starter/blob/master/CONTRIBUTORS.txt) if you have not yet done so.
* Join the [IRC channel #pyramid on irc.freenode.net](https://webchat.freenode.net/?channels=pyramid).
## Git Branches
- Submit pull requests to the [`master` branch](https://github.com/Pylons/pyramid-cookiecutter-starter/tree/master). This branch is *not* the default and must be selected instead of [`latest`]. See the [README.rst, under Versions](https://github.com/Pylons/pyramid-cookiecutter-starter#versions).
- For development, create a new branch. If changes on your new branch are accepted, they will be merged into the master branch and deployed.
* Submit pull requests to the [`master` branch](https://github.com/Pylons/pyramid-cookiecutter-starter/tree/master).
This branch is *not* the default and must be selected instead of `latest`.
See the [README.rst, under Versions](https://github.com/Pylons/pyramid-cookiecutter-starter/#versions).
* For development, create a new branch.
If changes on your new branch are accepted, they will be merged into the master branch and deployed.
## Prerequisites

No commit comments for this range