Merge branch 'main' into remove_reflect

.github/ISSUE_TEMPLATE/question.md

@@ -1,12 +1,10 @@
 ---
 name: ask a question
-about: ask us question - assume stackoverflow's guidelines apply here
-title: 'q: ( your question title goes here )'
+about: ask a question - assume stackoverflow's guidelines apply here
+title: your question title goes here
 labels: 'kind/question, status/triage, area/v2'
 assignees: ''
 
 ---
 
-## my question is...
-
-_**( Put the question text here )**_
+my question is...

.github/ISSUE_TEMPLATE/v1-bug-report.md

@@ -1,28 +1,32 @@
 ---
 name: v1 bug report
 about: Create a report to help us fix v1 bugs
-title: 'v1 bug: ( your bug title goes here )'
+title: 'your bug title goes here'
 labels: 'kind/bug, status/triage, area/v1'
 assignees: ''
 
 ---
 
-## my urfave/cli version is
+## My urfave/cli version is
 
 _**( Put the version of urfave/cli that you are using here )**_
 
 ## Checklist
 
-* [ ] Are you running the latest v1 release? The list of releases is [here](https://github.com/urfave/cli/releases).
-* [ ] Did you check the manual for your release? The v1 manual is [here](https://github.com/urfave/cli/blob/master/docs/v1/manual.md)
-* [ ] Did you perform a search about this problem? Here's the [Github guide](https://help.github.com/en/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests) about searching.
+- [ ] Are you running the latest v1 release? The list of releases is [here](https://github.com/urfave/cli/releases).
+- [ ] Did you check the manual for your release? The v1 manual is [here](https://github.com/urfave/cli/blob/main/docs/v1/manual.md).
+- [ ] Did you perform a search about this problem? Here's the [Github guide](https://help.github.com/en/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests) about searching.
 
 ## Dependency Management
 
-- [ ] My project is using go modules.
-- [ ] My project is using vendoring.
-- [ ] My project is automatically downloading the latest version.
-- [ ] I am unsure of what my dependency management setup is.
+<!--
+  Delete any of the following that do not apply:
+-->
+
+- My project is using go modules.
+- My project is using vendoring.
+- My project is automatically downloading the latest version.
+- I am unsure of what my dependency management setup is.
 
 ## Describe the bug
 
@@ -34,23 +38,30 @@ Describe the steps or code required to reproduce the behavior
 
 ## Observed behavior
 
-What did you see happen immediately after the reproduction steps above?
+What did you see happen immediately after the reproduction steps
+above?
 
 ## Expected behavior
 
-What would you have expected to happen immediately after the reproduction steps above?
+What would you have expected to happen immediately after the
+reproduction steps above?
 
 ## Additional context
 
 Add any other context about the problem here.
 
-If the issue relates to a specific open source Github repo, please link that repo here.
+If the issue relates to a specific open source Github repo, please
+link that repo here.
 
-If you can reproduce this issue with a public CI system, please link a failing build here.
+If you can reproduce this issue with a public CI system, please
+link a failing build here.
 
 ## Want to fix this yourself?
 
-We'd love to have more contributors on this project! If the fix for this bug is easily explained and very small, free free to create a pull request for it. You'll want to base the PR off the `v1` branch, all `v1` bug fix releases will be made from that branch.
+We'd love to have more contributors on this project! If the fix for
+this bug is easily explained and very small, free free to create a
+pull request for it. You'll want to base the PR off the `v1`
+branch, all `v1` bug fix releases will be made from that branch.
 
 ## Run `go version` and paste its output here
 

.github/ISSUE_TEMPLATE/v2-bug-report.md

@@ -1,28 +1,32 @@
 ---
 name: v2 bug report
 about: Create a report to help us fix v2 bugs
-title: 'v2 bug: ( your bug title goes here )'
+title: 'your bug title goes here'
 labels: 'kind/bug, area/v2, status/triage'
 assignees: ''
 
 ---
 
-## my urfave/cli version is
+## My urfave/cli version is
 
 _**( Put the version of urfave/cli that you are using here )**_
 
 ## Checklist
 
-* [ ] Are you running the latest v2 release? The list of releases is [here](https://github.com/urfave/cli/releases).
-* [ ] Did you check the manual for your release? The v2 manual is [here](https://github.com/urfave/cli/blob/master/docs/v2/manual.md)
-* [ ] Did you perform a search about this problem? Here's the [Github guide](https://help.github.com/en/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests) about searching.
+- [ ] Are you running the latest v2 release? The list of releases is [here](https://github.com/urfave/cli/releases).
+- [ ] Did you check the manual for your release? The v2 manual is [here](https://github.com/urfave/cli/blob/main/docs/v2/manual.md)
+- [ ] Did you perform a search about this problem? Here's the [Github guide](https://help.github.com/en/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests) about searching.
 
 ## Dependency Management
 
-- [ ] My project is using go modules.
-- [ ] My project is using vendoring.
-- [ ] My project is automatically downloading the latest version.
-- [ ] I am unsure of what my dependency management setup is.
+<!--
+  Delete any of the following that do not apply:
+-->
+
+- My project is using go modules.
+- My project is using vendoring.
+- My project is automatically downloading the latest version.
+- I am unsure of what my dependency management setup is.
 
 ## Describe the bug
 
@@ -34,23 +38,30 @@ Describe the steps or code required to reproduce the behavior
 
 ## Observed behavior
 
-What did you see happen immediately after the reproduction steps above?
+What did you see happen immediately after the reproduction steps
+above?
 
 ## Expected behavior
 
-What would you have expected to happen immediately after the reproduction steps above?
+What would you have expected to happen immediately after the
+reproduction steps above?
 
 ## Additional context
 
 Add any other context about the problem here.
 
-If the issue relates to a specific open source Github repo, please link that repo here.
+If the issue relates to a specific open source Github repo, please
+link that repo here.
 
-If you can reproduce this issue with a public CI system, please link a failing build here.
+If you can reproduce this issue with a public CI system, please
+link a failing build here.
 
 ## Want to fix this yourself?
 
-We'd love to have more contributors on this project! If the fix for this bug is easily explained and very small, free free to create a pull request for it.
+We'd love to have more contributors on this project! If the fix for
+this bug is easily explained and very small, free free to create a
+pull request for it.
+
 ## Run `go version` and paste its output here
 
 ```

.github/ISSUE_TEMPLATE/v2-feature-request.md

@@ -1,7 +1,7 @@
 ---
 name: v2 feature request
 about: Suggest an improvement for v2
-title: 'v2 feature: ( your feature title goes here )'
+title: 'your feature title goes here'
 labels: 'type/feature, area/v2, status/triage'
 assignees: ''
 
@@ -10,21 +10,25 @@ assignees: ''
 ## Checklist
 
 * [ ] Are you running the latest v2 release? The list of releases is [here](https://github.com/urfave/cli/releases).
-* [ ] Did you check the manual for your release? The v2 manual is [here](https://github.com/urfave/cli/blob/master/docs/v2/manual.md)
+* [ ] Did you check the manual for your release? The v2 manual is [here](https://github.com/urfave/cli/blob/main/docs/v2/manual.md).
 * [ ] Did you perform a search about this feature? Here's the [Github guide](https://help.github.com/en/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests) about searching.
 
 ## What problem does this solve?
 
 A clear and concise description of what problem this feature would solve. For example:
 
-- needing to type out the full flag name takes a long time, so I would like to suggest adding auto-complete
-- I use (osx, windows, linux) and would like support for (some existing feature) to be extended to my platform
-- the terminal output for a particular error case is confusing, and I think it could be improved
+- needing to type out the full flag name takes a long time, so I
+  would like to suggest adding auto-complete
+- I use (osx, windows, linux) and would like support for (some
+  existing feature) to be extended to my platform
+- the terminal output for a particular error case is confusing, and
+  I think it could be improved
 
 ## Solution description
 
 A detailed description of what you want to happen.
 
 ## Describe alternatives you've considered
 
-A clear and concise description of any alternative solutions or features you've considered.
+A clear and concise description of any alternative solutions or
+features you've considered.

.github/pull_request_template.md

@@ -8,10 +8,14 @@
 
 _(REQUIRED)_
 
-- [ ] bug
-- [ ] cleanup  
-- [ ] documentation
-- [ ] feature
+<!--
+  Delete any of the following that do not apply:
+ -->
+
+- bug
+- cleanup
+- documentation
+- feature
 
 ## What this PR does / why we need it:
 
@@ -28,6 +32,7 @@ _(REQUIRED)_
 ## Which issue(s) this PR fixes:
 
 _(REQUIRED)_
+
 <!--
 If this PR fixes one of more issues, list them here.
 One line each, like so:

.github/stale.yml

@@ -1,64 +1,17 @@
-# Configuration for probot-stale - https://github.com/probot/stale
-
-# Number of days of inactivity before an Issue or Pull Request becomes stale
-daysUntilStale: 90
-
-# Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
-# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
-daysUntilClose: 30
-
-# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
-onlyLabels: []
-
-# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 365
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 90
+# Issues with these labels will never be considered stale
 exemptLabels:
   - pinned
   - security
-  - "help wanted"
-  - "kind/maintenance" 
-
-# Set to true to ignore issues in a project (defaults to false)
-exemptProjects: false
-
-# Set to true to ignore issues in a milestone (defaults to false)
-exemptMilestones: false
-
-# Set to true to ignore issues with an assignee (defaults to false)
-exemptAssignees: false
-
-# Label to use when marking as stale
-staleLabel: "status/stale"
-
-# Comment to post when marking as stale. Set to `false` to disable
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+# Comment to post when marking an issue as stale. Set to `false` to disable
 markComment: >
-  This issue or PR has been automatically marked as stale because it has not had
-  recent activity. Please add a comment bumping this if you're still
-  interested in it's resolution! Thanks for your help, please let us know
-  if you need anything else.
-
-# Comment to post when removing the stale label.
-unmarkComment: >
-  This issue or PR has been bumped and is no longer marked as stale! Feel free
-  to bump it again in the future, if it's still relevant.
-
-# Comment to post when closing a stale Issue or Pull Request.
-closeComment: >
-  Closing this as it has become stale.
-
-# Limit the number of actions per hour, from 1-30. Default is 30
-limitPerRun: 30
-
-# Limit to only `issues` or `pulls`
-# only: issues
-
-# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
-# pulls:
-#   daysUntilStale: 30
-#   markComment: >
-#     This pull request has been automatically marked as stale because it has not had
-#     recent activity. It will be closed if no further activity occurs. Thank you
-#     for your contributions.
-
-# issues:
-#   exemptLabels:
-#     - confirmed
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false