Polish the Closed Bugs GH workflow - #46271
Merged
Merged
Conversation
Remove the attempts to have these issues land in the same 'inbox' (the existing project board for triage). Since they're closed, the automated workflow of the project board will move them to the 'Closed' column/status even with the API call specifically moving them to 'Incoming' instead. It is what it is, we'll have a separate project board for this. Also: - don't look at comments on PRs - don't freak out if the issue has no type - add a permissions block as a defensive measure (in case someone adds secrets.GITHUB_TOKEN later) - add a timeout to avoid hanging out for six hours or whatever the default is - add some logging.
cla-bot
Bot
added
the
cla-signed
rtfeldman
pushed a commit
that referenced
this pull request
Jan 9, 2026
Remove the attempts to have these issues land in the same 'inbox' (the existing project board for triage). Since they're closed, the automated workflow of the project board will move them to the 'Closed' column/status even with the API call specifically moving them to 'Incoming' instead. It is what it is, we'll have a separate project board for this. Also: - don't look at comments on PRs - don't freak out if the issue has no type - add a permissions block as a defensive measure (in case someone adds secrets.GITHUB_TOKEN later) - add a timeout to avoid hanging out for six hours or whatever the default is - add some logging. Release Notes: - N/A
jonx
pushed a commit
to jonx/zed-aros
that referenced
this pull request
Jul 17, 2026
Remove the attempts to have these issues land in the same 'inbox' (the existing project board for triage). Since they're closed, the automated workflow of the project board will move them to the 'Closed' column/status even with the API call specifically moving them to 'Incoming' instead. It is what it is, we'll have a separate project board for this. Also: - don't look at comments on PRs - don't freak out if the issue has no type - add a permissions block as a defensive measure (in case someone adds secrets.GITHUB_TOKEN later) - add a timeout to avoid hanging out for six hours or whatever the default is - add some logging. Release Notes: - N/A
jolutz
pushed a commit
to jolutz/zed
that referenced
this pull request
Aug 8, 2026
Remove the attempts to have these issues land in the same 'inbox' (the existing project board for triage). Since they're closed, the automated workflow of the project board will move them to the 'Closed' column/status even with the API call specifically moving them to 'Incoming' instead. It is what it is, we'll have a separate project board for this. Also: - don't look at comments on PRs - don't freak out if the issue has no type - add a permissions block as a defensive measure (in case someone adds secrets.GITHUB_TOKEN later) - add a timeout to avoid hanging out for six hours or whatever the default is - add some logging. Release Notes: - N/A
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
1 participant
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.
Remove the attempts to have these issues land in the same 'inbox' (the existing project board for triage). Since they're closed, the automated workflow of the project board will move them to the 'Closed' column/status even with the API call specifically moving them to 'Incoming' instead. It is what it is, we'll have a separate project board for this.
Also:
Release Notes: