1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Commit graph

15 commits

Author SHA1 Message Date
Dag Wieers
3db8b75f35
Remove slashes from instructions to avoid confusion 2017-12-15 17:18:31 +01:00
John R Barker
7654195716
Avoid people listing component in comment 2017-12-13 15:47:29 +00:00
Dag Wieers
e76e8aed90
Fix closing tag for COMPONENT NAME, multiline changes 2017-12-13 10:18:37 +01:00
John R Barker
390a17f0eb
Update ISSUE_TEMPLATE.md 2017-11-30 13:19:07 +00:00
Toshio Kuratomi
c82cf791dd Add a code-smell test for smart quotes and remove smart quotes from all files 2017-09-18 16:49:16 -07:00
Brian Coca
83ef5237cd added note about ansible-config to issue template 2017-09-18 12:33:26 -04:00
John R Barker
830ad2351f Ask for Network OS version info (#25958) 2017-06-21 12:55:55 +01:00
Dag Wieers
8a25b2477c Remove the hint to report module issue elsewhere. 2016-12-14 11:30:44 -05:00
Matt Clay
1da20c9716 Clean up issue templates. (#19011)
* Remove legacy GitHub templates.
* Remove references to module repos.
2016-12-08 17:18:30 -05:00
Dag Wieers
947877dcce Try to avoid module-related tickets in the core Ansible project (#17047)
* Try to avoid module-related tickets in the core Ansible project

Since most users still report module-related problems in the Ansible core GitHub project, I added a warning at the top of the template.

Maybe it could help if the various projects would have more specific names ?

 - ansible/ansible  ->  ansible/main (or something even better ?)
 - ansible/ansible-modules-core  ->  ansible/modules-core
 - ansible/ansible-modules-extras  ->  ansible/modules-extras

I am sure someone can come up with perfect names ;-)

* Remove 'module' from the component options

I would prefer to again note that modules should go elsewhere, but don't want to bloat the text too much.
2016-08-11 10:14:27 -04:00
jctanner
df81f1197f Add Component Name to the issue and pr templates (#17019) 2016-08-09 13:18:06 -04:00
Dag Wieers
f9c4fdab40 Move comments out of code-blocks (#15961)
In hindsight, I think it is better to have empty code-blocks
then comment placeholders when people don't replace those sections.
2016-05-23 15:37:17 -04:00
Dag Wieers
e4701b12ee One more improvement 2016-03-23 14:00:55 +01:00
Dag Wieers
2e9fc91844 Various improvements to issue/pull-request templates
- Instruct to verify if an issue/request already exists
- Use uppercase for titles (easier to parse as titles)
- Remove empty lines where it makes sense (instructions)
- Ensure that commit-message appears directly under summary (pull-requests)
2016-03-23 13:49:20 +01:00
Dag Wieers
1afa369eec Move the Github issue and pull-request templates to .github
In essence, most people do not need to use the templates directly,
getting them out of the way increases the signal-to-noise ratio of
the root directory. Direct people to what they are looking for.
2016-03-10 13:55:49 +01:00
Renamed from ISSUE_TEMPLATE.md (Browse further)