da86f5e042
Developers run all sorts of different tools within Git repositories, any of which can leave their own special trashfiles all over the place. We can't every hope to catalog them all, so better to recommend developers simply configure a global core.excludesfile to filter the irrelevant files which tend to get created by their personal choice of tools. To this end, remove the long-standing sections for "Mr Developer" and "Editors" since their mere existence here sends the signal that we welcome (and have time to review) additions for any old tool someone ever might happen to try. Also add a comment block explaining this, for clarity. We can, and should of course, continue to list files created by the tools recommended by our workflow (test frameworks called from tox, documentation and packaging builds, et cetera). Change-Id: Ib58a57267b064e4142686de6c37a70dbff04b9a7 |
||
---|---|---|
hooks | ||
{{cookiecutter.repo_name}} | ||
.gitignore | ||
.gitreview | ||
CONTRIBUTING.rst | ||
README.rst | ||
cookiecutter.json |
README.rst
cookiecutter-openstack
Cookiecutter template for an OpenStack project. See https://github.com/audreyr/cookiecutter.
- Free software: Apache license
- pbr: Set up to use Python Build Reasonableness
- hacking: Enforces the OpenStack Hacking Guidelines
- stestr: Runs tests using stestr
- OpenStack-Infra: Ready for OpenStack Continuous Integration testing
- Tox testing: Setup to easily test for Python 2.7, 3.5
- Sphinx docs: Documentation ready for generation and publication
Usage
Install cookiecutter:
pip install cookiecutter
Generate a Python package project:
cookiecutter https://git.openstack.org/openstack-dev/cookiecutter.git
OpenStack projects require a working git repo for pbr to work, on newer versions of cookiecutter (>= 0.7.0 released 2013-11-09) this initial commit will be done automatically. Otherwise you will need to init a repo and commit to it before doing anything else:
cd $repo_name
git init
git add .
git commit -a
Then:
- Add the project to the OpenStack Infrastructure