Update auto comments to make them more uniform

4f7695b0ce0575260ee606d723af22736e0f6896

Wolfsblvt <wolfsblvt@gmail.com>

Parents: 5f726d2b2516269f55271885c82a8360dfac0b40

.github/issues-auto-comments.yml+23 -18 Viewed

 -comment:
 -  footer: >
 -    ---
 -    > I am a bot, and this is an automated message 🤖
 labels:
   - name: ✖️ Invalid
     labeled:
       issue:
         action: close
         body: >
           HelloHey @{{ issue.user.login }}., Yourthis ticketissue has been marked as invalid.
 -          Please ensure you follow the issue template, provide all requested info,
++
 -          and be sure to check the docs + previous issues prior to raising tickets.
 +          Please double-check that you've followed the issue template, included all necessary details, and reviewed the docs & previous issues before submitting.
 +          If provided, follow the instructions given by maintainers.
   - name: 👩‍💻 Good First Issue
     labeled:
       issue:
         body: >
           🏆 This issue has been marked as a good first issue for contributors to implement!
           This is a great way to support the project. While also improving your skills, you'll also be credited as a contributor once your PR is merged.
++
           If you're new to SillyTavern [here is the official documentation](https://docs.sillytavern.app/). The official contribution guide can be found [here](https://github.com/SillyTavern/SillyTavern/blob/release/CONTRIBUTING.md).
           If you need any support at all, feel free to reach out via [Discord](https://discord.gg/sillytavern), or let us know in this issue or via [discussions](https://github.com/SillyTavern/SillyTavern/discussions).
   - name: ❌ wontfix
     labeled:
       issue:
         action: close
         body: >
           ❌ This ticketissue has been marked as 'wontfix', which usually means it is out-of-scope, or not feasible at this time or will not be implemented for various reasons.
           IFIf you have any questions about this, feel free to reach out.
++
 +  - name: 🛑 Out of Scope
 +    labeled:
 +      issue:
 +        action: close
 +        body: >
 +          🛑 This issue has been marked as 'out of scope', as this can't or won't be implemented.
 +          If you have any questions about this, feel free to reach out.
   - name: ✅ Done (staging)
     labeled:
       issue:
         body: >
           ✅ It looks like all or part of this issue has now been implemented as part of the `staging` branch.
           If you currently are on the `release` branch, you can switch to `staging` to test this right away.
           Note that `staging` is considered less stable than the official releases. To switch, follow existing instructions,

     labeled:
       issue:
         body: >
           ✅ It looks like all or part of this issue has now been implemented as part of the `latest` release.
   - name: ‼️ High Priority
     labeled:
       issue:
         body: >
                       🚨 This issue has been marked as high priority, indicating thatmeaning it is's important to the maintainers and theor community.
                       While we cannot guaranteecan't anpromise immediate fix or provide an exact timelinechanges, please rest assured that it is on our radar and will be addressed whenever possible. Thanks for your patience!
 -            Thank you for your patience and understanding.
   - name: 💀 Spam
     labeled:

         locking: lock
         lock_reason: spam
         body: >
           💀 This issue has been identifiedflagged as spam, and is now locked.
           Please refrain fromavoid posting spam in the future, as- it disrupts the community and wastes valuableeveryone's time.

.github/pr-auto-comments.yml+17 -13 Viewed

 -comment:
 -  footer: >
 -    ---
 -    > I am a bot, and this is an automated message 🤖
 labels:
   - name: ✖️ Invalid
     labeled:
       pr:
         action: close
         body: >
           Thank youHey @{{ pull_request.user.login }} for, contributingthanks tofor thisyour repository.contribution!
           YourUnfortunately, Pullthis RequestPR has been marked as invalid.
 -          Please ensure you follow the pull request template, provide all relevant info,
 +          Please check that you've followed the PR template, included all relevant details, and are targeting the correct branch (`staging` for regular contributions, `release` only for hotfixes).
 -          and target the correct branch. `staging` is the default target branch, `release` should only be targeted for important hotfixes.
           If you have anyneed questionshelp, feel free to reach out.ask!
   - name: ⛔ Don't Merge
     labeled:
       pr:
         body: >
           🚨 This PR has been temporarily blocked from merging.
   - name: 💥💣 Breaking Changes
     labeled:
       pr:
         body: >
           This PR is marked⚠️ asHeads containingup! oneThis orPR moreintroduces breaking changes.
           Please makeMake sure thatthese thosechanges are well-documented accordingly and stepsthat tousers informwill usersbe atproperly releaseinformed arewhen preparedthis is released.
   - name: ⛔ Waiting For External/Upstream
     labeled:
       pr:
         body: >
             ⛔ This PR is awaiting external or upstream changes or approval.
             It can only be merged once those changes have been implemented and approved.
++
             Please inform us of any progress on the upstream changes or approval.
++
 +  - name: 🔬 Needs Testing
 +    labeled:
 +      pr:
 +        body: >
 +          🔬 This PR needs testing!
 +          Any contributor can test and leave reviews, so feel free to help us out!
++

.github/workflows/job-close-stale.yml+13 -12 Viewed

           remove-stale-when-updated: true
           enable-statistics: true
           stale-issue-message: >
             ⏳ This issue has gone 6been monthsinactive withoutfor an6 updatemonths. To keep the ticket open, please indicate thatIf it is's still relevant, indrop a comment below to keep it open.
             Otherwise, it will be auto-closed in 7 days.
           stale-pr-message: >
             ⏳ This PR is stale because it has been openinactive for 6 months with no activity. Either removeIf theit's stalestill labelrelevant, orupdate commentit belowor withremove athe shortstale update,label.
             otherwise thisOtherwise, PRit will be auto-closed in 7 days.
           close-issue-message: >
             🔒 This issue was automatically auto-closed because it hasdue beento stalledinactivity for over 6 months with no activity.
           close-pr-message: >
             This🔒 pullThis requestPR was automatically auto-closed because it hasdue beento stalledinactivity for over 6 months with no activity.
           stale-issue-label: '⚰️ Stale'
           close-issue-label: '🕸️ Inactive'
           stale-pr-label: '⚰️ Stale'

           operations-per-run: 30
           remove-stale-when-updated: true
           stale-issue-message: >
             Hi⚠️ Hey! LooksWe likeneed additionalsome more info isto requiredmove forforward with this issue to be addressed.
             Don'tPlease forgetprovide tothe providerequested thisdetails withinin the next few days to keep yourthis ticket open.
           close-issue-message: >
             Issue🔒 This issue was auto-closed due to no response from user.
           only-labels: '🚏 Awaiting User Response'
           labels-to-remove-when-unstale: '🚏 Awaiting User Response'
           stale-issue-label: '🛑 No Response'

           operations-per-run: 30
           remove-stale-when-updated: true
           stale-issue-message: >
 -            This issue was marked as having an alternative solution available. Did this help you out, and this issue can be closed?
 +            🔄 An alternative solution has been provided for this issue.
 -            Please confirm by commenting to keep it open, otherwise it will be closed in 7 days.
 +            Did this solve your problem? If so, we'll go ahead and close it.
 +            If you still need help, drop a comment within the next 7 days to keep this open.
           close-issue-message: >
             Issue✅ closedClosing automaticallythis issue due to no confirmation regardingon the alternative solution.
           only-labels: '🚧 Alternative Exists'
           stale-issue-label: '🚏 Awaiting User Response'
           close-issue-label: '🕸️ Inactive'

.github/workflows/pr-auto-manager.yml+5 -5 Viewed

         with:
           dirtyLabel: '🚫 Merge Conflicts'
           repoToken: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
 -          commentOnDirty: "This pull request has conflicts. Please resolve them, otherwise it cannot be merged."
 +          commentOnDirty: >
 +            ⚠️ This PR has conflicts that need to be resolved before it can be merged.
   pr-size-labeler:
     name: Apply Label for PR Size

           xl_label: 'PR - XL'
           fail_if_xl: 'false'
           message_if_xl: >
             ⚠️ This PR exceedsis theover recommended1000 sizelines, ofwhich 1000is lineslarger than recommended.
 -            Please ensure you are not addressing multiple issues in one PR.
++
 -            Note this PR might be rejected due to its size.
 +            Please make sure that it only addresses a single issue - PRs this large are hard to test and may be rejected.
           github_api_url: 'https://api.github.com'
           files_to_ignore: |
             "package-lock.json"

           for ISSUE in $(echo $final_issues | jq -r '.[]'); do
             echo "Updating issue #$ISSUE"
             gh issue edit $ISSUE -R ${{ github.repository }} --add-label "✅ Done (staging)"
 -            gh issue comment $ISSUE -R ${{ github.repository }} -b "This issue is now available in the \`staging\` branch for testing. Please verify and let us know any feedback!"
           done