Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Follow Ansible Galaxy best practices #8

Open
ferrarimarco opened this issue Jan 30, 2017 · 1 comment
Open

Follow Ansible Galaxy best practices #8

ferrarimarco opened this issue Jan 30, 2017 · 1 comment

Comments

@ferrarimarco
Copy link
Contributor

ferrarimarco commented Jan 30, 2017 •
edited
Loading

Currently this cookiecutter is not following at least three of the Ansible Galaxy best practices:

  1. README.md should be formatted with markdown: see pull request Use Markdown in README. For #8 #9
  2. Prefix variable names with the role name: can be fixed by editing this line
  3. Integrate your roles with Travis CI: for this one I opened an issue (Implement a test infrastructure #6) and a pull request (Implement a test infrastructure. For #6 #7)

Thoughts?
@ferrarimarco ferrarimarco changed the title Follow Ansible Galaxy best practivìces Follow Ansible Galaxy best practices Jan 30, 2017
ferrarimarco added a commit to ferrarimarco/cookiecutter-ansible-role that referenced this issue Feb 9, 2017
@ferrarimarco
Use Markdown in README. For iknite#8
711d90b 
Ansible Galaxy best practices advise on using
Markdown to format the README.
Source: https://galaxy.ansible.com/intro#readme
@ferrarimarco ferrarimarco mentioned this issue Feb 9, 2017
Merged
iknite added a commit that referenced this issue Feb 13, 2017
@iknite
Merge pull request #9 from ferrarimarco/feat/markdown-readme
2e59ee6 
Use Markdown in README. For #8
@ferrarimarco
Copy link
Contributor Author

@iknite I implemented point no.2 here in my fork. Let me know if you are interested, I can prepare a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ferrarimarco