ansible/hacking/deprecated_issue_template.md

##### SUMMARY
%(component)s contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal

```
%(path)s:%(line)s:%(column)s: %(msg)s
```

##### ISSUE TYPE
 - Bug Report

##### COMPONENT NAME
```
%(path)s
```

##### ANSIBLE VERSION
```
%(version)s
```

##### CONFIGURATION
N/A

##### OS / ENVIRONMENT
N/A

##### STEPS TO REPRODUCE
N/A

##### EXPECTED RESULTS
N/A

##### ACTUAL RESULTS
N/A
pylint plugin to catch due/past-due deprecated calls (#44143) * Start of work on pylint plugin to catch due/past-due deprecated calls * Improve deprecated pylint plugin * Catch call to AnsibleModule.deprecate also * Skip splatted kwargs, we can't infer that info * Add error for invalid version in deprecation * Skip version if it's a reference to a var * Disable ansible-deprecated-no-version for displaying deprecated module info * fix comments * is None * Force specifying a version, this can be disabled on a per case basis * Disable ansible-deprecated-version by default * Remove to look for 2.8 deprecated * Revert "Remove to look for 2.8 deprecated" This reverts commit 4e84034fd104879f429f0262ff0b2317e3d08deb. * Add script and template used for creating issues for deprecated issues * Fix underscore var 6 years ago			`##### SUMMARY`
			`%(component)s contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal`

			```
			`%(path)s:%(line)s:%(column)s: %(msg)s`
			```

			`##### ISSUE TYPE`
			`- Bug Report`

			`##### COMPONENT NAME`
			```
			`%(path)s`
			```

			`##### ANSIBLE VERSION`
			```
			`%(version)s`
			```

			`##### CONFIGURATION`
			`N/A`

			`##### OS / ENVIRONMENT`
			`N/A`

			`##### STEPS TO REPRODUCE`
			`N/A`

			`##### EXPECTED RESULTS`
			`N/A`

			`##### ACTUAL RESULTS`
			`N/A`