Merge branch 'release' into staging

8cbdf6bb8188b660c8d1cd9073f9a9bfdf9a8cab

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

.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: 360183
           days-before-close: 57
           operations-per-run: 30
           remove-stale-when-updated: true
           enable-statistics: true
           stale-issue-message: >
             This issue has gone 36 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 working7 days.
           stale-pr-message: >
             This PR is stale because it has been open 6 weeksmonths with no activity. Either remove the stale label or comment below with a short update,
             otherwise this PR will be closed in 57 days.
           close-issue-message: >
             This issue was automatically closed because it has been stalled for over 16 yearmonths with no activity.
           close-pr-message: >
             This pull request was automatically closed because it has been stalled for over 16 yearmonths 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: 57
           days-before-close: 37
           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: 365183
           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.
 -5. 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.
 +5. 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?
 +6. 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.