Repository navigation
Add one-shot workflow to close the Comunity Release milestone (issue 13) - #14
Closed
QuasarAppCI wants to merge 1 commit into
Closed
QuasarAppCI wants to merge 1 commit into
QuasarAppCI wants to merge 1 commit into
Conversation
Closed
Member
|
@QuasarAppCI no - release means close all issues in milistone. This workflow is not required. |
Member
Author
|
Understood — the workflow is not required; PR closed (not merged) and the orphaned One factual note: the QuasarAppCI account currently has read-only (pull) access on this repository, so it cannot close issues or manage labels (verified: GraphQL Please pick one:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task issue_13 "Comunity Release"
Issue #13 asks to close the "Comunity Release" milestone with all its issues.
The QuasarAppCI bot account only has read (pull) access on this repository
(no triage / maintain / push), so it cannot close issues or manage labels
directly:
closeIssue-> "QuasarAppCI does not have the correct permissions to executeCloseIssue"PATCH /issues/{n}(state=closed) -> 403 "Must have admin rights to Repository"This PR adds a one-shot, manually triggered workflow
.github/workflows/close-community-release.ymlthat runs with the repositoryGITHUB_TOKEN(issues: write,milestones: write) and:Usage (maintainer):
The workflow is
workflow_dispatch-only (never runs automatically) and can bedeleted from the repository after the first successful run.
Alternative: grant the
QuasarAppCIaccount maintain permission on therepository and the agent will close the issues and milestone directly in the
next cycle (no workflow needed).