ansible - ansible

	Commit message (Collapse)	Author	Age	Files	Lines
*	Split the unified PR template into few (#82734)	Sviatoslav Sydorenko (Святослав Сидоренко)	2024-03-07	1	-25/+1
\| \| \|	Ref: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository
*	Update bot link in the GH templates (#81390)	Martin Krizek	2023-08-03	1	-4/+0
\| \| \| \|	Also remove "Component Name" section from the PR template as components are automatically detected by the bot from the list of changed files.
*	Add pymarkdown sanity test for core (#81220)	Matt Clay	2023-07-11	1	-0/+6
\| \| \| \| \| \| \|	* Clean up markdown * Add pymarkdown sanity test for core * Update unit test SHA
*	Modernize GitHub pull-request template (#70787)	Rick Elrod	2020-07-21	1	-1/+1
\| \| \| \| \| \| \| \| \|	Change: - Remove "New Module Pull Request" since we're not taking new modules in ansible/ansible - Add "Tests Pull Request" to use for things like adding coverage that aren't bugfixes. Signed-off-by: Rick Elrod <rick@elrod.me>
*	Remove ansible version from PR template.	Matt Clay	2018-11-13	1	-6/+0
\| \| \| \|	While important for issues, it adds almost no value for PRs.
*	Improve GitHub templates (#44455)	Dag Wieers	2018-09-04	1	-17/+13
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Improve GitHub templates The existing templates are basically a copy for each type of issue (bug, feature, doc) whereas we can make the template more specific to the task at hand. This PR includes: - More specific sections depending on the type of issue - More concise and direct instructions (NO NEED FOR FRUSTRATION CAPS!) - Single-line comments (no need to guide people to avoid wrong edits) - Improved paste area - Better headings/titles - No 'Summary' title for PRs (so commit information is placed correctly) This PR would require some improvements to Ansibot. * Remove controversial Ansibot stuff Make it easier to get the first batch merged. * Restore ISSUE_TEMPLATE.md * Incorporate reviewer suggestions * Make OS / ENVIRONMENT doc-related * Rephrase Ansibot-related message
*	[github] Replace second 'module' with 'feature' in PR template comment (#43478)	joren485	2018-07-31	1	-1/+1
\|
*	Update Issue & PR templates to make them clearer	John Barker	2018-04-17	1	-8/+4
\| \| \| \|	Try and reduce people typing in the comments section
*	Remove slashes from instructions to avoid confusion	Dag Wieers	2017-12-15	1	-1/+1
\|
*	Add a code-smell test for smart quotes and remove smart quotes from all files	Toshio Kuratomi	2017-09-19	1	-1/+1
\|
*	Move summary to be next to where github places the commit message. (#22368)	Toshio Kuratomi	2017-03-07	1	-7/+15
\| \| \| \| \| \| \|	If a user makes a PR with a single, detailed commit message, github will put that at the top of the PR. Move our summary field to the top of the PR template so that it is next to where the commit message is placed. Users can then easily merge the two together or supplement the commit message with additional information that we ask for.
*	Clean up issue templates. (#19011)	Matt Clay	2016-12-08	1	-1/+1
\| \| \| \| \|	* Remove legacy GitHub templates. * Remove references to module repos.
*	Add Component Name to the issue and pr templates (#17019)	jctanner	2016-08-09	1	-0/+3
\|
*	Move comments out of code-blocks (#15961)	Dag Wieers	2016-05-23	1	-2/+4
\| \| \| \|	In hindsight, I think it is better to have empty code-blocks then comment placeholders when people don't replace those sections.
*	Various improvements to issue/pull-request templates	Dag Wieers	2016-03-23	1	-12/+7
\| \| \| \| \| \| \|	- 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)
*	Move the Github issue and pull-request templates to .github	Dag Wieers	2016-03-10	1	-0/+29
	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.