vikarti.anatra/safing-portbase
1
0
Fork 0
mirror of https://github.com/safing/portbase synced 2025-09-01 18:19:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add new issue management workflows

Browse source
This commit is contained in:
Daniel 2023-08-29 18:01:23 +02:00
parent d481098e66
commit 4490d27b55
6 changed files with 107 additions and 116 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

74
.github/stale.yml vendored
View file

@ -1,74 +0,0 @@
# Configuration for probot-stale - https://github.com/probot/stale
# Limit to only `issues` or `pulls`
only: issues
# Number of days of inactivity before an Issue or Pull Request becomes stale
daysUntilStale: 21
# Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
daysUntilClose: 7
# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
onlyLabels: []
# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels:
- "priority support"
- faq
- dependencies
- pinned
- security
# Set to true to ignore issues in a project (defaults to false)
exemptProjects: false
# Set to true to ignore issues in a milestone (defaults to false)
exemptMilestones: false
# Set to true to ignore issues with an assignee (defaults to false)
exemptAssignees: false
# Label to use when marking as stale
staleLabel: inactive
# Comment to post when marking as stale. Set to `false` to disable
markComment: >
This issue has been automatically marked as inactive because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
# Comment to post when removing the stale label.
# unmarkComment: >
# Your comment here.
# Comment to post when closing a stale Issue or Pull Request.
closeComment: >
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.
If the issue has not been resolved, you can find more information or continue the conversation here:
- [Docs & FAQ](https://docs.safing.io/)
- [Wiki](https://wiki.safing.io/)
- [Get Help on Discord](https://discord.gg/safing)
Please keep in mind that the free version of Portmaster only has limited support. We can only give so much limited free support.
If you find our work brings value to you, please consider supporting it by purchasing Supporter or Unlimited Packages https://safing.io/pricing/.
If you already are a paying subscriber and want to claim priority support for this issue, please send us a message [on Discord](https://discord.gg/safing) or [via Email](mailto:support@safing.io) with your username and the link to this issue, so we can prioritize accordingly.
# Limit the number of actions per hour, from 1-30. Default is 30
# limitPerRun: 30
# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
# pulls:
# daysUntilStale: 30
# markComment: >
# This pull request 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.
# issues:
# exemptLabels:
# - confirmed

19
.github/workflows/greetings.yml vendored
View file

@ -1,19 +0,0 @@
name: Greetings
on: [issues]
jobs:
greeting:
runs-on: ubuntu-latest
permissions:
issues: write
# pull-requests: write
steps:
- uses: actions/first-interaction@v1
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
issue-message: |
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
🗣️ On [Discord](https://discord.gg/safing) the community is super helpful and active, we also have a support bot there which will give you immediate help
📖 The [Wiki](https://wiki.safing.io/) answers almost all questions, if you cant find your solution there let us know so we can add the missing info's
# pr-message: "Message that will be displayed on users' first pull request"

25
.github/workflows/issues-first-greet.yml vendored Normal file
View file

@ -0,0 +1,25 @@
# This workflow responds to first time posters with a greeting message.
# Docs: https://github.com/actions/first-interaction
name: Greet New Users
# This workflow is triggered when a new issue is created.
on:
issues:
types: opened
jobs:
greet:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- uses: actions/first-interaction@v1
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
# Respond to first time issue raisers.
issue-message: |
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
- 🗣️ Our community on [Discord](https://discord.gg/safing) is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
- 📖 The [Wiki](https://wiki.safing.io/) answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

39
.github/workflows/issues-label-responder.yml vendored Normal file
View file

@ -0,0 +1,39 @@
# This workflow responds with a message when certain labels are added to an issue or PR.
# Docs: https://github.com/hramos/respond-to-issue-based-on-label
name: Respond To Issues Based on Label
# This workflow is triggered when a label is added to an issue.
on:
issues:
types: labeled
jobs:
respond:
name: Process Label Action
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Process Label Action
uses: hramos/respond-to-issue-based-on-label@v2
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
community support:
comment: |
Thank you for raising this issue with us.
After a first review we noticed that this does not seem to be a technical issue, but rather a configuration issue or general question about how Portmaster works.
Thus, we invite the community to help with configuration and/or answering this questions.
If you are in a hurry or haven't received an answer, a good place to ask is in [our Discord community](https://discord.gg/safing).
If your problem or question has been resolved or answered, please come back and give an update here for other users encountering the same and then close this issue.
If you are a paying subscriber and want this issue to be checked out by Safing, please send us a message [on Discord](https://discord.gg/safing) or [via Email](mailto:support@safing.io) with your username and the link to this issue, so we can prioritize accordingly.
need debug info:
comment: |
Thank you for raising this issue with us.
After a first review we noticed that we will require the Debug Info for further investigation. However, you haven't supplied any Debug Info in your report.
Please [collect Debug Info](https://wiki.safing.io/en/FAQ/DebugInfo) from _while_ the reported issue is present.

43
.github/workflows/issues-stale.yml vendored Normal file
View file

@ -0,0 +1,43 @@
# This workflow warns and then closes stale issues and PRs.
# Docs: https://github.com/actions/stale
name: Close Stale Issues
on:
schedule:
- cron: "17 5 * * 1-5" # run at 5:17 (UTC) on Monday to Friday
jobs:
stale:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- uses: actions/stale@v5
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
# Handle stale issues
stale-issue-label: 'stale'
# Exemptions
exempt-issue-assignees: 'dhaavi,Raphty'
exempt-issue-labels: 'support,faq,dependencies,pinned,security'
# Mark as stale
days-before-issue-stale: 63 # 2 months / 9 weeks
stale-issue-message: |
This issue has been automatically marked as inactive because it has not had activity in the past two months.
If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.
# Close
days-before-issue-close: 7 # 1 week
close-issue-message: |
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.
If the issue has not been resolved, you can find more information or continue the conversation here:
- [Wiki & FAQ](https://wiki.safing.io/)
- [Get Help on Discord](https://discord.gg/safing)
Please keep in mind that the free version of Portmaster only has limited support. If you find our work brings value to you, please consider supporting it by purchasing Portmaster Plus or Pro: https://safing.io/pricing/.
If you already are a paying subscriber and want this issue to be checked out by Safing, please send us a message [on Discord](https://discord.gg/safing) or [via Email](mailto:support@safing.io) with your username and the link to this issue, so we can prioritize accordingly.
# TODO: Handle stale PRs

23
auto-comment.yml
View file

@ -1,23 +0,0 @@
issueOpened: >
Thank you for reaching out.
In case you are raising an issue, you can find more information to try to it yourself here:
- [Wiki & FAQ](https://wiki.safing.io/)
- [GitHub Issues](https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Asafing+sort%3Aupdated-desc)
- [Ask on Discord](https://discord.gg/safing)
Additionally, there is a __ChatGPT-like support bot__ trained on our documentation, that you can [ask for help in this Discord channel](https://discord.com/channels/389815143711637517/1106170808704974878).
Please keep in mind that the free version of Portmaster only has community support and inactive issues are automatically closed after a while.
If you find our work brings value to you, please consider supporting it by purchasing Supporter or Unlimited Packages https://safing.io/pricing/.
If you are a customer, first of all: Thank You!
If you want to claim priority support for this issue, please send us a message [on Discord](https://discord.gg/safing) or [via Email](mailto:support@safing.io) with your username and the link to this issue, so we can prioritize accordingly.
pullRequestOpened: >
Thank you for your pull request.
If you have not already, please read our [contribution guideline](https://wiki.safing.io/en/Contribute).
If this change is bigger and you have not discussed it with us, please head over to [Discord](https://discord.gg/safing) to discuss your idea.