From a6a4eee66b704de16c624336786df8e26a9aadf5 Mon Sep 17 00:00:00 2001 From: Jason Cooke Date: Thu, 27 Jun 2019 16:01:31 +1200 Subject: [PATCH 1/4] docs: fix typo (#1362) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index adf34e007..1b523321f 100644 --- a/README.md +++ b/README.md @@ -170,7 +170,7 @@ If you want to report a security vulnerability, please follow the steps which we ## Core Team -The core team is the responsable for drive this project, team is ordered by antiquity and areas of responsability. +The core team is the responsable for drive this project, team is ordered by antiquity and areas of responsibility. | [Juan Picado](https://github.com/juanpicado) | [Ayush Sharma](https://github.com/ayusharma) | [Sergio Hg](https://github.com/sergiohgz) | [Priscila Oliveria](https://github.com/priscilawebdev) | |---|---|---|---| From 0177241504ce0af6847a74d6705c8bf75e2f1a36 Mon Sep 17 00:00:00 2001 From: James George Date: Sat, 29 Jun 2019 09:43:45 +0530 Subject: [PATCH 2/4] Minor tweaks typo fix and grammar --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1b523321f..2e7518419 100644 --- a/README.md +++ b/README.md @@ -170,7 +170,7 @@ If you want to report a security vulnerability, please follow the steps which we ## Core Team -The core team is the responsable for drive this project, team is ordered by antiquity and areas of responsibility. +The core team is responsible for driving this project ahead, team is ordered by antiquity and areas of responsibility. | [Juan Picado](https://github.com/juanpicado) | [Ayush Sharma](https://github.com/ayusharma) | [Sergio Hg](https://github.com/sergiohgz) | [Priscila Oliveria](https://github.com/priscilawebdev) | |---|---|---|---| From 41310ca0fb395910c97c4181f00e2b4c6be2d26e Mon Sep 17 00:00:00 2001 From: "Juan Picado @jotadeveloper" Date: Sat, 29 Jun 2019 10:18:12 +0200 Subject: [PATCH 3/4] chore: update stale config Inspired by gatsby community adding this message --- .github/stale.yml | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/.github/stale.yml b/.github/stale.yml index 99d65e9ab..d53a44644 100644 --- a/.github/stale.yml +++ b/.github/stale.yml @@ -1,7 +1,7 @@ # Number of days of inactivity before an issue becomes stale -daysUntilStale: 30 +daysUntilStale: 15 # Number of days of inactivity before a stale issue is closed -daysUntilClose: 5 +daysUntilClose: 10 # Issues with these labels will never be considered stale exemptLabels: - dev: high priority @@ -13,8 +13,14 @@ exemptLabels: staleLabel: issue: wontfix # Comment to post when marking an issue as stale. Set to `false` to disable markComment: > - 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. + Hi pal πŸ‘‹πŸΌ! + + This issue has gone quiet 😢. + + We get a lot of issues, so we currently close issues after 25 days of inactivity. It’s been at least 15 days since the last update here. + If we missed this issue or if you want to keep it open, please reply here. You can also add/suggest the label "discuss" to keep this issue open! + As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out [https://github.com/verdaccio/contributing](https://github.com/verdaccio/contributing) for more information about opening PRs, triaging issues, and contributing! + + Thanks for being a part of the Verdaccio community! πŸ’˜ # Comment to post when closing a stale issue. Set to `false` to disable closeComment: false From acf5a791f6c685f5e471ceb59b6b2ad6338c016a Mon Sep 17 00:00:00 2001 From: "Juan Picado @jotadeveloper" Date: Sat, 29 Jun 2019 11:38:22 +0200 Subject: [PATCH 4/4] chore: update lock settings --- .github/lock.yml | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/.github/lock.yml b/.github/lock.yml index 9e0e17855..aa8c27d65 100644 --- a/.github/lock.yml +++ b/.github/lock.yml @@ -1,7 +1,7 @@ # Configuration for lock-threads - https://github.com/dessant/lock-threads # Number of days of inactivity before a closed issue or pull request is locked -daysUntilLock: 200 +daysUntilLock: 90 # Issues and pull requests with these labels will not be locked. Set to `[]` to disable exemptLabels: [] @@ -11,9 +11,15 @@ 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. + πŸ€–This thread has been automatically locked πŸ”’ since there has not been + any recent activity after it was closed. + + We lock tickets after 90 days with the idea to encourage you to open a ticket with new fresh data + and to provide you better feedback 🀝and better visibility πŸ‘€. + + If you consider, can attach this ticket πŸ“¨to the new one as a reference for better context. + + Thanks for being a part of the Verdaccio community! πŸ’˜ # Limit to only `issues` or `pulls` # only: issues @@ -25,4 +31,4 @@ issues: lockLabel: outdated pulls: - daysUntilLock: 90 + daysUntilLock: 10