Upload 10 files

.github/workflows/add-comment-from-tag.yml

@@ -0,0 +1,28 @@
+# Based on a label applied to an issue, the bot will add a comment with some additional info
+
+name: 🎯 Auto-Reply to Labeled Tickets
+on:
+  issues:
+    types:
+      - labeled
+      - unlabeled
+  pull_request_target:
+    types:
+      - labeled
+      - unlabeled
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  comment:
+    runs-on: ubuntu-20.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2     
+      - name: Label Commenter
+        uses: peaceiris/actions-label-commenter@v1
+        with:
+          config_file: .github/issue-auto-comments.yml
+          github_token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}

.github/workflows/check-merge-conflicts.yml

@@ -0,0 +1,17 @@
+# Detect and label pull requests that have merge conflicts
+name: 🏗️ Check Merge Conflicts
+on:
+  push:
+    branches:
+    - staging
+jobs:
+  check-conflicts:
+    if: github.repository == 'SillyTavern/SillyTavern'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: mschilde/auto-label-merge-conflicts@master
+        with:
+          CONFLICT_LABEL_NAME: "🚫 Merge Conflicts"
+          GITHUB_TOKEN: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          MAX_RETRIES: 5
+          WAIT_MS: 5000

.github/workflows/close-stale-issues.yml

@@ -0,0 +1,82 @@
+# Closes any issues that no longer have user interaction
+name: 🎯 Close Stale Issues
+
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 0 * * *' # Runs every day at midnight UTC
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    steps:
+      # Comment on, then close issues that haven't been updated for ages 
+      - name: Close Stale Issues
+        uses: actions/stale@v4
+        with:
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          days-before-stale: 183
+          days-before-close: 7
+          operations-per-run: 30
+          remove-stale-when-updated: true
+          enable-statistics: true
+          stale-issue-message: > 
+            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 7 days.
+          stale-pr-message: >
+            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 7 days.
+          close-issue-message: >
+            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 6 months with no activity.
+          stale-issue-label: '⚰️ Stale'
+          close-issue-label: '🕸️ Inactive'
+          stale-pr-label: '⚰️ Stale'
+          close-pr-label: '🕸️ Inactive'
+          exempt-issue-labels: '📌 Keep Open'
+          exempt-pr-labels: '📌 Keep Open'
+          labels-to-add-when-unstale: '📌 Keep Open'
+          
+        # Comment on, then close issues that required a response from the user, but didn't get one
+      - name: Close Issues without Response
+        uses: actions/stale@v4
+        with:
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          days-before-stale: 7
+          days-before-close: 7
+          operations-per-run: 30
+          remove-stale-when-updated: true
+          stale-issue-message: >
+            Hi! Looks like additional info is required for this issue to be addressed.
+            Don't forget to provide this within the next few days to keep your ticket open.
+          close-issue-message: 'Issue closed due to no response from user.'
+          only-labels: '🚏 Awaiting User Response'
+          labels-to-remove-when-unstale: '🚏 Awaiting User Response, 🛑 No Response'
+          stale-issue-label: '🛑 No Response'
+          close-issue-label: '🕸️ Inactive'
+          exempt-issue-labels: '📌 Keep Open'
+          exempt-pr-labels: '📌 Keep Open'
+          
+        # Comment on issues that we should have replied to
+      - name: Notify Repo Owner to Respond
+        uses: actions/stale@v4
+        with:
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          days-before-stale: 7
+          days-before-close: 183
+          operations-per-run: 30
+          remove-stale-when-updated: true
+          stale-issue-message: Hey SillyTavern, - Don't forget to respond!
+          stale-pr-message: Hey SillyTavern, - Don't forget to respond!
+          only-labels: '👤 Awaiting Maintainer Response'
+          labels-to-remove-when-unstale: '👤 Awaiting Maintainer Response'
+          close-issue-message: 'Closed due to no response from repo author for over a year'
+          close-pr-message: 'Closed due to no response from repo author for over a year'
+          stale-issue-label: '👤 Awaiting Maintainer Response'
+          stale-pr-label: '👤 Awaiting Maintainer Response'
+          close-issue-label: '🕸️ Inactive'
+          close-pr-label: '🕸️ Inactive'
+          exempt-issue-labels: '📌 Keep Open'
+          exempt-pr-labels: '📌 Keep Open'

.github/workflows/docker-publish.yml

@@ -0,0 +1,94 @@
+# This workflow will publish a docker image for every full release to the GitHub package repository
+
+name: Create Docker Image (Release and Staging)
+
+on:
+  release:
+    # Allow pre-releases
+    types: [published]
+  schedule:
+    # Build the staging image everyday at 00:00 UTC
+    - cron: "0 0 * * *"
+  push:
+    # Temporary workaround
+    branches:
+      - release
+
+env:
+  # This should allow creation of docker images even in forked repositories
+  REPO: ${{ github.repository }}
+  REGISTRY: ghcr.io
+
+jobs:
+  build:
+    if: github.repository == 'SillyTavern/SillyTavern'
+    runs-on: ubuntu-latest
+
+    steps:
+      # Workaround for GitHub repo names containing uppercase characters
+      - name: Set lowercase repo name
+        run: |
+          echo "IMAGE_NAME=${REPO,,}" >> ${GITHUB_ENV}
+
+      # Using the following workaround because currently GitHub Actions
+      # does not support logical AND/OR operations on triggers
+      # It's currently not possible to have `branches` under the `schedule` trigger
+      - name: Checkout the release branch (on release)
+        if: ${{ github.event_name == 'release' || github.event_name == 'push' }}
+        uses: actions/[email protected]
+        with:
+          ref: "release"
+
+      - name: Checkout the staging branch
+        if: ${{ github.event_name == 'schedule' }}
+        uses: actions/[email protected]
+        with:
+          ref: "staging"
+
+      # Get current branch name
+      # This is also part of the workaround for Actions not allowing logical
+      # AND/OR operators on triggers
+      # Otherwise the action triggered by schedule always has ref_name = release
+      - name: Get the current branch name
+        run: |
+          echo "BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)" >> ${GITHUB_ENV}
+
+      # Setting up QEMU for multi-arch image build
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v3
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Extract metadata (tags, labels) for the image
+        uses: docker/[email protected]
+        id: metadata
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          # Release version tag if the workflow is triggered by a release
+          # Branch name tag if the workflow is triggered by a push
+          # Latest tag if the branch is release and the workflow is triggered by a push
+          tags: |
+            ${{ github.event_name == 'release' && github.ref_name || env.BRANCH_NAME }}
+            ${{ github.event_name == 'push' && env.BRANCH_NAME == 'release' && 'latest' || '' }}
+
+      # Login into package repository as the person who created the release
+      - name: Log in to the Container registry
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      # Build docker image using dockerfile for amd64 and arm64
+      # Tag it with branch name
+      # Assumes branch name is the version number
+      - name: Build and push
+        uses: docker/[email protected]
+        with:
+          context: .
+          platforms: linux/amd64,linux/arm64
+          file: Dockerfile
+          push: true
+          tags: ${{ steps.metadata.outputs.tags }}
+          labels: ${{ steps.metadata.outputs.labels }}

.github/workflows/get-pr-size.yml

@@ -0,0 +1,39 @@
+# Adds a comment to new PRs, showing the compressed size and size difference of new code
+# And also labels the PR based on the number of lines changes
+
+name: 🌈 Check PR Size
+on: [pull_request]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout
+      uses: actions/checkout@v2
+    # Find and comment with compressed size
+    - name: Get Compressed Size
+      uses: preactjs/compressed-size-action@v2
+      with:
+        repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+        pattern: './dist/**/*.{js,css,html}'
+        strip-hash: '\\b\\w{8}\\.'
+        exclude: '**/node_modules/**'
+        minimum-change-threshold: 100
+    # Check number of lines of code added
+    - name: Label based on Lines of Code
+      uses: codelytv/pr-size-labeler@v1
+      with:
+        GITHUB_TOKEN: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+        xs_max_size: '10'
+        s_max_size: '100'
+        m_max_size: '500'
+        l_max_size: '1000'
+        s_label: '🟩 PR - Small'
+        m_label: '🟨 PR - Medium'
+        l_label: '🟧 PR - Large'
+        xl_label: '🟥 PR - XL'
+        fail_if_xl: 'false'
+        message_if_xl: >
+          It looks like this PR is very large (over 1000 lines).
+          Try to avoid addressing multiple issues in a single PR, and
+          in the future consider breaking large tasks down into smaller steps.
+          This it to make reviewing, testing, reverting and general quality management easier.

.github/workflows/labeler.yml

@@ -0,0 +1,19 @@
+name: "Issue Labeler"
+on:
+  issues:
+    types: [opened, edited]
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: github/[email protected]
+      with:
+        configuration-path: .github/labeler.yml
+#        not-before: 2020-01-15T02:54:32Z # optional and will result in any issues prior to this timestamp to be ignored.
+        enable-versioned-regex: 0
+        repo-token: ${{ github.token }}

.github/workflows/manage-pending-labels-closed.yml

@@ -0,0 +1,17 @@
+# When a new comment is added to an issue, if it had the Stale or Awaiting User Response labels, then those labels will be removed
+
+name: 🎯 Remove Pending Labels on Close
+on:
+  issues:
+    types: [closed]
+jobs:
+  remove-labels:
+   runs-on: ubuntu-latest
+   steps:
+   - name: Remove Labels when Closed
+     uses: actions-cool/issues-helper@v2
+     with:
+      actions: remove-labels
+      token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: '🚏 Awaiting User Response,⚰️ Stale,👤 Awaiting Maintainer Response'

.github/workflows/manage-pending-labels.yml

@@ -0,0 +1,42 @@
+# When a new comment is added to an issue, if it had the Stale or Awaiting User Response labels, then those labels will be removed
+
+name: 🎯 Add/ Remove Awaiting Response Labels
+on:
+  issue_comment:
+    types: [created]
+jobs:
+  remove-stale:
+   runs-on: ubuntu-latest
+   if: ${{ github.event.comment.author_association != 'COLLABORATOR' && github.event.comment.author_association != 'OWNER' }}
+   steps:
+   - name: Remove Stale labels when Updated
+     uses: actions-cool/issues-helper@v2
+     with:
+      actions: remove-labels
+      token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: '🚏 Awaiting User Response,⚰️ Stale'
+
+  add-awaiting-author:
+   runs-on: ubuntu-latest
+   if: ${{!github.event.issue.pull_request && github.event.comment.author_association != 'COLLABORATOR' && github.event.comment.author_association != 'OWNER' && github.event.issue.state == 'open' }}
+   steps:
+   - name: Add Awaiting Author labels when Updated
+     uses: actions-cool/issues-helper@v2
+     with:
+      actions: add-labels
+      token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: '👤 Awaiting Maintainer Response'
+
+  remove-awaiting-author:
+   runs-on: ubuntu-latest
+   if: ${{ github.event.comment.author_association == 'OWNER' }}
+   steps:
+   - name: Remove Awaiting Author labels when Updated
+     uses: actions-cool/issues-helper@v2
+     with:
+      actions: remove-labels
+      token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: '👤 Awaiting Maintainer Response'

.github/workflows/npm-publish.yml

@@ -0,0 +1,32 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+      - run: npm ci
+
+  publish-npm:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.npm_token}}

.github/workflows/update-i18n.yaml

@@ -0,0 +1,32 @@
+name: Update i18n data
+
+on: workflow_dispatch
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:                # Job-level permissions configuration starts here
+      contents: write           # 'write' access to repository contents
+    steps:
+    - name: disable auto crlf
+      uses: steve02081504/disable-autocrlf@v1
+    - uses: actions/checkout@v4
+      with:
+        ref: ${{ github.head_ref }}
+        fetch-depth: 0 # otherwise, there would be errors pushing refs to the destination repository.
+    - name: Create local changes
+      run: |
+        aria2c https://raw.githubusercontent.com/SillyTavern/SillyTavern-i18n/main/generate.py
+        aria2c https://raw.githubusercontent.com/SillyTavern/SillyTavern-i18n/main/requirements.txt
+        pip install -r ./requirements.txt
+        python ./generate.py "" --sort-keys
+        rm -f ./generate.py ./requirements.txt
+    - name: add all
+      run: git add -A
+    - name: push
+      uses: actions-go/push@master
+      with:
+        author-email: 41898282+github-actions[bot]@users.noreply.github.com
+        author-name: github-actions[bot]
+        commit-message: 'i18n changes'
+        remote: origin