Scope Martian triage to bug-labeled issues for jlowin#3124
Conversation
marvin-context-protocol
Bot
added
the
enhancement
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1f8d5ef825
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| (github.event.action == 'opened' && github.actor == 'strawgate') || | ||
| (github.event.action == 'opened' && github.actor == 'jlowin' && contains(github.event.issue.labels.*.name, 'bug')) || | ||
| (github.event.action == 'labeled' && github.event.label.name == 'triage-martian' && contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.sender.author_association)) |
There was a problem hiding this comment.
As written, the job only runs for opened events where the bug label is already present. If jlowin opens an issue without the label and it’s applied later by a labeler or maintainer (a common workflow), the labeled event won’t trigger triage because it only checks for triage-martian. That means legitimate bug issues opened by jlowin will skip triage entirely unless the label is set at creation. Consider handling the labeled event for bug as well if the intent is “triage whenever a jlowin issue has a bug label.”
Useful? React with 👍 / 👎.
1 participant
Strawgate-opened issues still always trigger Martian triage. For jlowin-opened issues, triage now only runs when the issue has a
buglabel, avoiding unnecessary triage on feature discussions and other non-bug issues.