47487469e9
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. Add a comment block explaining this, for clarity, and remove the one current editor-specific entry present. We can, and should of course, continue to list files created by the tools recommended by our workflow (test frameworks, documentation and packaging builds, et cetera). This change is a port of Ib58a57267b064e4142686de6c37a70dbff04b9a7 from the openstack-dev/cookiecutter repository. Change-Id: Ib79f8e857cc71d5e7ddbaf856e29f2548c624f52
Team and repository tags
puppet-openstack-cookiecutter
Cookiecutter template for a compliant OpenStack puppet-modules
Installation
Install cookiecutter either from source, pip or package if it exists
Usage
There are two ways to create the boilerplate for the puppet module.
Locally
- Clone locally the puppet-openstack-cookiecutter repository.
- Run
cookiecutter /path/to/cloned/repo
Remotely (ie. using a git repo)
- Run
cookiecutter https://git.openstack.org/openstack/puppet-openstack-cookiecutter.git
What's next
Once the boilerplate created, in order to be compliant with the other modules, the files managed by msync, (or configs) needs to be in the project folder. Once synced module is ready, announce its existence to the ML, make the proper patch to openstack-infra and finally wait for the reviews to do the rest.