6 Commits (b8448fdb9026f6de03087d431a2f489cc9dcf428)

Author	SHA1	Message	Date
Toshio Kuratomi	43ba8813d3	Move summary to be next to where github places the commit message. (#22368) ... 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.	8 years ago
Matt Clay	1da20c9716	Clean up issue templates. (#19011) ... * Remove legacy GitHub templates. * Remove references to module repos.	8 years ago
jctanner	df81f1197f	Add Component Name to the issue and pr templates (#17019)	8 years ago
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.	9 years ago
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)	9 years ago
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.	9 years ago