[cordova] branch master updated: chore: improve the issue tracker process (#210)

[er...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

erisu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cordova.git


The following commit(s) were added to refs/heads/master by this push:
     new ae81330  chore: improve the issue tracker process (#210)
ae81330 is described below

commit ae813308876126a38d7169690e586aae914b8773
Author: エリス <er...@users.noreply.github.com>
AuthorDate: Tue May 24 01:53:28 2022 +0900

    chore: improve the issue tracker process (#210)
    
    * chore: add stale bot process
    * chore: add request-info bot process
    * chore: add lock bot process
    * chore: add no-response bot process
---
 .github/config.yml      | 35 +++++++++++++++++++++++++++++++++++
 .github/lock.yml        | 26 ++++++++++++++++++++++++++
 .github/no-response.yml | 20 ++++++++++++++++++++
 .github/stale.yml       | 27 +++++++++++++++++++++++++++
 4 files changed, 108 insertions(+)

diff --git a/.github/config.yml b/.github/config.yml
new file mode 100644
index 0000000..19f4955
--- /dev/null
+++ b/.github/config.yml
@@ -0,0 +1,35 @@
+# The "request-info" app is used to automatically alert users when they have created a
+# new issues that does not have any description. We will reassure them that we need information
+# to be able to help them. It will also say they should follow the issue template that was
+# pre-provided when creating the issue.
+
+requestInfoReplyComment: >
+  Thank you for your submission, however, with the lack of information, we are unable
+  to continue at this time.
+
+  We would appreciate it if you could provide us with more information about this
+  submission so that we could provide better support to this issue/pr.
+
+  Therefore, please edit this issue accordingly by using our pre-provided template or
+  close and create a new one and make sure to provide all the required information.
+
+  This submission will be automatically closed later if no information is provided.
+
+# Titles can also be checked against for lack of descriptiveness. (MUST BE ALL LOWERCASE)
+# requestInfoDefaultTitles:
+#   - update readme.md
+#   - updates
+
+# Append the info-needed label issues and prs with insufficient information.
+requestInfoLabelToAdd: info-needed
+
+# Issues and PR requires more information than what is provided in the templates
+# This check will will fail if the body matches the provided template
+checkIssueTemplate: true
+checkPullRequestTemplate: true
+
+# Only warn about insufficient information on these events types
+# Keys must be lowercase. Valid values are 'issue' and 'pullRequest'
+requestInfoOn:
+  pullRequest: true
+  issue: true
diff --git a/.github/lock.yml b/.github/lock.yml
new file mode 100644
index 0000000..40a80f6
--- /dev/null
+++ b/.github/lock.yml
@@ -0,0 +1,26 @@
+# The "lock" app is used to lock the threads of a closed issues or prs after (x) number of days of inactivity.
+# This is to help prevent long-lived issues and prs after being resolved. If users still have issues after
+# a closed PR or issue thread is locked, they should create a new issue. The locking of the thread does not
+# occur immedatly after an issue or PR is closed. Users will still have an opportunity to re-open the issue.
+# They can always back-link to an old locked issue in a new issue if they believe it is the one and the same.
+
+# The number of days of inactivity before a closed issue or pr is locked
+daysUntilLock: 14
+
+# Skip issues and prs created before a given timestamp. ISO 8601 Timestamp `YYYY-MM-DD` or `false` to disable
+skipCreatedBefore: false
+
+# Issues and pr with these labels will be ignored. `[]` to disable
+exemptLabels: []
+
+# The label to add before locking. `false` to disable
+lockLabel: false
+
+# Comment to post before locking. Set to `false` to disable
+lockComment: >
+  This thread has been automatically locked since there has not been
+  any recent activity after it was closed. Please open a new issue for
+  related bugs.
+
+# Assign `resolved` as the reason for locking. Set to `false` to disable
+setLockReason: true
diff --git a/.github/no-response.yml b/.github/no-response.yml
new file mode 100644
index 0000000..af1a04a
--- /dev/null
+++ b/.github/no-response.yml
@@ -0,0 +1,20 @@
+# The "no-response" app is used to automatically close issues that have not received a response
+# from the author. This app is paired with the "request-info" app which manages the warning
+# and label pinning.
+
+# Notice: This app does not support PRs. While the "request-info" app still warns users in PRs,
+# PRs will need to be managed manually for the closing.
+
+# The number of days of inactivity before an issue is closed for lack of response
+daysUntilClose: 4
+
+# The pinned label requiring a response
+responseRequiredLabel: info-needed
+
+# Comment to post when closing an issue for lack of response. `false` to disable
+closeComment: >
+  This issue has been automatically closed because there has been no response
+  to our request for more information from the original author. With only the
+  information that is currently in the issue, we don't have enough information
+  to take action. Please reach out if you have or find the answers we need so
+  that we can investigate further.
diff --git a/.github/stale.yml b/.github/stale.yml
new file mode 100644
index 0000000..f081bd4
--- /dev/null
+++ b/.github/stale.yml
@@ -0,0 +1,27 @@
+# The "Stale" app is used to automatically close stale issues and pr which accumulates over time.
+
+# The number of days of inactivity before an issue or pr is flagged as stale with the stale tag.
+daysUntilStale: 60
+
+# The number of days of inactivity before a stale issue is closed
+daysUntilClose: 14
+
+# The issues and pr that contains any of these labels will never be flagged as stale
+exemptLabels:
+  - pinned
+  - security
+
+# The label which is appened to mark an issue or pr as stale
+staleLabel: wontfix
+
+# Below is the stale bot's comment to warn users when a issue or pr becomes stale.
+markComment: >
+This has been automatically marked as stale due to the lack of activity. It will be closed if no further activity occurs.
+
+If you believe this is still valid, please provide an update to reassure that it is needed and all open questions were answered.
+When verifying, please use the master branch as this may have already been resolved.
+
+Thank you for your contributions.
+
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org