Most issues include parts of the advice from the template, which adds noise to tickets.
E.g. A lot of tickets include the text "Please pick one and delete the rest:"
By adding the advice to the user as comments (<!--- comment -->) we achieve two important things:
1. The advice does not end up in the actual issue ticket or pull request
2. It is easier for the user to differentiate its own input and the original advice
(And my help them to clean up the advice as well, which in fact is now no longer necessary)
Prior to 75b6f61, we strictly limited variables we re-injected. After that
patch however, we re-injected everything which causes problems under certain
circumstances. For now, we'll continue to filter out some properties of
PlayContext for re-injection.
Fixes#14352
QA had asked me a while ago to clean up the way the precedence list for 1.x was worded,
as the intro from the list started with "then comes", as if something should preceed
it. The comments from OxABAB were not helpful themselves, but his issue reminded me that
this was on my to do list to make a little cleaner and clearer. Edits made to remove the
"then comes" intros for each list line, to help with clarity.
This is related to #14559, but only the part for Ansible v2.0
This commit makes merging empty dicts, or equal dicts more efficient.
I noticed that while debugging merge_hash a lot of merges related to empty dictionaries and sometimes also identical dictionaries.
Now that Github supports separate issue and PR templates, we can have a
separate cut-down version for PRs without all the things we ask for in a
new issue. The PR types are also removed from the ISSUE_TEMPLATE.
The old template was effusive at the expense of making the text harder
to read and easier to miss things in. This one is more direct, and easy
to scan quickly.
will display on certain verbosity levels, both playbook/file info
and non empty options with which it's running.
avoid errors when not using CLI classes