4312391e0a
(B) This is a work in progress but the idea is to have text snippets where we can respond to tickets with a bit more helpful info. Not active just yet.
26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
Cleanup Request
|
|
===============
|
|
|
|
Hi!
|
|
|
|
Thanks very much for your submission to Ansible. It sincerely means a lot to us.
|
|
|
|
We do require submissions to be free of merge commits, which cause difficulties in reviewing and merging code, and also affect the history of the source tree.
|
|
To resolve this problem, it may be helpful to create a new branch and cherry-pick commits onto it.
|
|
|
|
* In general, always start a "topic branch" named after each thing you would like to contribute
|
|
* use "git pull --rebase" vs "git pull" to stay in tune with upstream, as well as "git rebase" vs "git merge"
|
|
* if you have things broken out over many commits, consider submitting just one squashed commit that keeps the history concise
|
|
|
|
Just as a quick reminder of things, this is a really busy project. We have over 800 contributors and to manage the queue effectively
|
|
we assign things a priority between P1 (highest) and P5. We'd like to thank you very much for your time!
|
|
We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgot about you!
|
|
|
|
We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly. You may also wish to join one of our two mailing lists
|
|
which is very active:
|
|
|
|
* https://groups.google.com/forum/#!forum/ansible-devel - for user questions, tips, and tricks
|
|
* https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
|
|
|
|
Thank you once again for this and your interest in Ansible!
|
|
|