Skip to content

Commit

Permalink
Add workflows for issue resolutions
Browse files Browse the repository at this point in the history
  • Loading branch information
andrewdavidwong committed Nov 14, 2023
1 parent 786aac6 commit c865290
Show file tree
Hide file tree
Showing 5 changed files with 160 additions and 0 deletions.
27 changes: 27 additions & 0 deletions .github/workflows/resolution-cannot-reproduce.yml
Original file line number Diff line number Diff line change
@@ -0,0 1,27 @@
name: Close issue with the resolution "cannot reproduce"
on:
issues:
types:
- labeled
jobs:
add-comment:
if: "github.event.label.name == 'R: cannot reproduce'"
runs-on: ubuntu-latest
permissions:
issues: write
steps:
- name: Create comment
uses: peter-evans/create-or-update-comment@v3
with:
issue-number: ${{ github.event.issue.number }}
body: |
This issue has been closed as "cannot reproduce." This means that attempts have been made to replicate the problem, but such attempts have not been reliably successful enough to proceed with fixing the problem.
We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community. If the problem becomes reliably reproducible in the future, please let us know in a comment below, and we will reopen this issue.
If anyone reading this believes that this issue was closed in error or that the resolution of "cannot reproduce" is not accurate, please leave a comment below, and we will review this issue again. For more information, see [How issues get closed](https://www.qubes-os.org/doc/issue-tracking/#how-issues-get-closed).
- name: Close Issue
uses: peter-evans/close-issue@v3
with:
issue-number: ${{ github.event.issue.number }}
close-reason: not_planned
35 changes: 35 additions & 0 deletions .github/workflows/resolution-declined.yml
Original file line number Diff line number Diff line change
@@ -0,0 1,35 @@
name: Close issue with the resolution "declined"
on:
issues:
types:
- labeled
jobs:
add-comment:
if: "github.event.label.name == 'R: declined'"
runs-on: ubuntu-latest
permissions:
issues: write
steps:
- name: Create comment
uses: peter-evans/create-or-update-comment@v3
with:
issue-number: ${{ github.event.issue.number }}
body: |
This issue has been closed as "declined." This means that the issue describes a legitimate bug (in the case of bug reports) or proposal (in the case of enhancements and tasks), and it is actionable. Nonetheless, it has been decided that no action will be taken on this issue. Here are some examples of reasons why an issue may be declined:
- No solution can be found.
- The proposed action is not possible.
- The proposed action would weaken security to an unacceptable degree.
- The proposed action would be too costly (in time, money, or other resources) relative to the benefits it would provide.
- The proposed action would make some things better while making other things worse, and the trade-off is not worthwhile.
These are just general examples. If the specific reason for this particular issue being declined has not already been provided, please feel free to leave a comment below asking for an explanation.
We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.
If anyone reading this believes that this issue was closed in error or that the resolution of "declined" is not accurate, please leave a comment below, and the Qubes team will review this issue again. For more information, see [How issues get closed](https://www.qubes-os.org/doc/issue-tracking/#how-issues-get-closed).
- name: Close Issue
uses: peter-evans/close-issue@v3
with:
issue-number: ${{ github.event.issue.number }}
close-reason: not_planned
33 changes: 33 additions & 0 deletions .github/workflows/resolution-duplicate.yml
Original file line number Diff line number Diff line change
@@ -0,0 1,33 @@
name: Close issue with the resolution "duplicate"
on:
issues:
types:
- labeled
jobs:
add-comment:
if: "github.event.label.name == 'R: duplicate'"
runs-on: ubuntu-latest
permissions:
issues: write
steps:
- name: Create comment
uses: peter-evans/create-or-update-comment@v3
with:
issue-number: ${{ github.event.issue.number }}
body: |
This issue has been closed as a "duplicate." This means that another issue exists that is very similar to or subsumes this one. If any useful information on this issue is not already present on the other issue, please add it in a comment on the other issue. Here are some common cases of duplicate issues:
- The other issue is closed. The other issue being closed does not prevent this issue from duplicating it. We will examine the closed issue and, if appropriate, reopen it.
- The other issue is for a different Qubes release. We usually maintain only one issue for all affected Qubes releases.
- The other issue is very old. The mere age of an issue is not, by itself, a relevant factor when determining duplicates.
By default, the newer issue will be closed in favor of the older issue. However, we make exceptions when we determine that it would be significantly more useful to keep the newer issue open instead of the older one.
We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.
If anyone reading this believes that this issue was closed in error or that the resolution of "duplicate" is not accurate, please leave a comment below, and we will review this issue again. For more information, see [How issues get closed](https://www.qubes-os.org/doc/issue-tracking/#how-issues-get-closed).
- name: Close Issue
uses: peter-evans/close-issue@v3
with:
issue-number: ${{ github.event.issue.number }}
close-reason: not_planned
38 changes: 38 additions & 0 deletions .github/workflows/resolution-not-applicable.yml
Original file line number Diff line number Diff line change
@@ -0,0 1,38 @@
name: Close issue with the resolution "not applicable"
on:
issues:
types:
- labeled
jobs:
add-comment:
if: "github.event.label.name == 'R: not applicable'"
runs-on: ubuntu-latest
permissions:
issues: write
steps:
- name: Create comment
uses: peter-evans/create-or-update-comment@v3
with:
issue-number: ${{ github.event.issue.number }}
body: |
This issue has been closed as "not applicable." Here are some common examples of cases in which issues are closed as not applicable:
- Help and support requests (please see [Help, support, mailing lists, and forum](https://www.qubes-os.org/support/))
- Questions (please see [Help, support, mailing lists, and forum](https://www.qubes-os.org/support/))
- Discussion issues (please see [Help, support, mailing lists, and forum](https://www.qubes-os.org/support/))
- Bug reports for behavior that is already working as intended
- Enhancement requests to improve things that are already working as intended
- Issues that rest on mistaken assumptions or misunderstandings
- Issues that do not provide enough information
- Issues that are not actionable
We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.
Regarding help and support requests, please note that this issue tracker (qubes-issues) is not intended to serve as a help desk or tech support center. Instead, we've set up other [venues where you can ask for help and support, ask questions, and have discussions](https://www.qubes-os.org/support/). By contrast, the issue tracker is more of a technical tool intended to support our developers in their work. We thank you for your understanding.
If anyone reading this believes that this issue was closed in error or that the resolution of "not applicable" is not accurate, please leave a comment below, and we will review this issue again. For more information, see [How issues get closed](https://www.qubes-os.org/doc/issue-tracking/#how-issues-get-closed).
- name: Close Issue
uses: peter-evans/close-issue@v3
with:
issue-number: ${{ github.event.issue.number }}
close-reason: not_planned
27 changes: 27 additions & 0 deletions .github/workflows/resolution-upstream-issue.yml
Original file line number Diff line number Diff line change
@@ -0,0 1,27 @@
name: Close issue with the resolution "upstream issue"
on:
issues:
types:
- labeled
jobs:
add-comment:
if: "github.event.label.name == 'R: upstream issue'"
runs-on: ubuntu-latest
permissions:
issues: write
steps:
- name: Create comment
uses: peter-evans/create-or-update-comment@v3
with:
issue-number: ${{ github.event.issue.number }}
body: |
This issue has been closed as an "upstream issue." This means that the issue pertains to software that does not belong to the Qubes OS Project and that we do not develop or control. We suggest that you file this issue in the appropriate project's issue tracker instead. For more information, see [Why don't you fix upstream bugs that affect Qubes OS?](https://www.qubes-os.org/faq/#why-dont-you-fix-upstream-bugs-that-affect-qubes-os)
We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.
If anyone reading this believes that this issue was closed in error or that the resolution of "upstream issue" is not accurate, please leave a comment below, and we will review this issue again. For more information, see [How issues get closed](https://www.qubes-os.org/doc/issue-tracking/#how-issues-get-closed).
- name: Close Issue
uses: peter-evans/close-issue@v3
with:
issue-number: ${{ github.event.issue.number }}
close-reason: not_planned

0 comments on commit c865290

Please sign in to comment.