starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[PR #3208] [MERGED] Add: workflow to close issues on release #3902

New Issue
Closed
opened 2026-04-25 00:17:30 +02:00 by adam · 0 comments
adam commented 2026-04-25 00:17:30 +02:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/advplyr/audiobookshelf/pull/3208
Author: @nichwall
Created: 7/30/2024
Status: ✅ Merged
Merged: 7/31/2024
Merged by: @advplyr

Base: master ← Head: release_issue_workflow

📝 Commits (2)

  • 6f5ffcb Add: workflow to close issues on release
  • 73e4293 Fix: label has space in name

📊 Changes

1 file changed (+20 additions, -0 deletions)

View changed files

➕ .github/workflows/close-issues-on-release.yml (+20 -0)

📄 Description

This PR adds a workflow to automatically do the following to issues with a label of awaiting release whenever a release is published:

  • Comment that it has been fixed with the current version number
  • Close issue (if open)
  • Remove awaiting release label

This workflow requires write permissions for issues, which is included in the workflow. The maintainer of the action I am using has not made a new release of the action since merging my PR to it, so I have just pinned the current SHA (not sure when they will get around to that).

I did not see any issues currently labeled as awaiting release that need to have the label removed before this workflow is ran. I tested this workflow in a personal repository and it worked well, but you may need to grant the workflow write permissions so it can access the write permissions on the issues (not 100% sure on the scoping there).

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/advplyr/audiobookshelf/pull/3208 **Author:** [@nichwall](https://github.com/nichwall) **Created:** 7/30/2024 **Status:** ✅ Merged **Merged:** 7/31/2024 **Merged by:** [@advplyr](https://github.com/advplyr) **Base:** `master` ← **Head:** `release_issue_workflow` --- ### 📝 Commits (2) - [`6f5ffcb`](https://github.com/advplyr/audiobookshelf/commit/6f5ffcb1f871c07b0e4e3c264dd699ee85e77d19) Add: workflow to close issues on release - [`73e4293`](https://github.com/advplyr/audiobookshelf/commit/73e4293f042d65e40f6298afb324eede2b1ffd40) Fix: label has space in name ### 📊 Changes **1 file changed** (+20 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/close-issues-on-release.yml` (+20 -0) </details> ### 📄 Description This PR adds a workflow to automatically do the following to issues with a label of `awaiting release` whenever a release is published: - Comment that it has been fixed with the current version number - Close issue (if open) - Remove `awaiting release` label This workflow [requires write permissions for issues](https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs), which is included in the workflow. The maintainer of the action I am using has not made a new release of the action since merging my PR to it, so I have just pinned the current SHA (not sure when they will get around to that). I did not see any issues currently labeled as `awaiting release` that need to have the label removed before this workflow is ran. I tested this workflow in a personal repository and it worked well, but you may need to grant the workflow write permissions so it can access the write permissions on the issues (not 100% sure on the scoping there). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2026-04-25 00:17:30 +02:00
adam closed this issue 2026-04-25 00:17:30 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3902
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?