Merge branch 'release' into staging

8cbdf6bb8188b660c8d1cd9073f9a9bfdf9a8cab

Cohee <18619528+Cohee1207@users.noreply.github.com>

Parents: 8892fdc421792f55843468578cf46ce5b18ed069 eac2e3d81e128c61299c94ef6c9dd1a8fd87a8c1

.github/workflows/close-stale-issues.yml+11 -11 Viewed

         uses: actions/stale@v4
         with:
           repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
-          days-before-stale: 360
+          days-before-stale: 183
-          days-before-close: 5
+          days-before-close: 7
           operations-per-run: 30
           remove-stale-when-updated: true
           enable-statistics: true
           stale-issue-message: >
-            This issue has gone 3 months without an update. To keep the ticket open, please indicate that it is still relevant in a comment below.
+            This issue has gone 6 months without an update. To keep the ticket open, please indicate that it is still relevant in a comment below.
-            Otherwise it will be closed in 5 working days.
+            Otherwise it will be closed in 7 days.
           stale-pr-message: >
-            This PR is stale because it has been open 6 weeks with no activity. Either remove the stale label or comment below with a short update,
+            This PR is stale because it has been open 6 months with no activity. Either remove the stale label or comment below with a short update,
-            otherwise this PR will be closed in 5 days.
+            otherwise this PR will be closed in 7 days.
           close-issue-message: >
-            This issue was automatically closed because it has been stalled for over 1 year with no activity.
+            This issue was automatically closed because it has been stalled for over 6 months with no activity.
           close-pr-message: >
-            This pull request was automatically closed because it has been stalled for over 1 year with no activity.
+            This pull request was automatically closed because it has been stalled for over 6 months with no activity.
           stale-issue-label: '⚰️ Stale'
           close-issue-label: '🕸️ Inactive'
           stale-pr-label: '⚰️ Stale'

         uses: actions/stale@v4
         with:
           repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
-          days-before-stale: 5
+          days-before-stale: 7
-          days-before-close: 3
+          days-before-close: 7
           operations-per-run: 30
           remove-stale-when-updated: true
           stale-issue-message: >

         with:
           repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
           days-before-stale: 7
-          days-before-close: 365
+          days-before-close: 183
           operations-per-run: 30
           remove-stale-when-updated: true
           stale-issue-message: Hey SillyTavern, - Don't forget to respond!

CONTRIBUTING.md+5 -1 Viewed

   - Updating GitHub Actions.
   - Hotfixing a critical bug.
 . Project maintainers will test and can change your code before merging.
-. Mind the license. Your contributions will be licensed under the GNU Affero General Public License. If you don't know what that implies, consult your lawyer.
+. Write at least somewhat meaningful PR descriptions. There's no "right" way to do it, but the following may help with outlining a general structure:
+  - What is the reason for a change?
+  - What did you do to achieve this?
+  - How would a reviewer test the change?
+. Mind the license. Your contributions will be licensed under the GNU Affero General Public License. If you don't know what that implies, consult your lawyer.