Skip to content

feat(aci): add exclusion to issue category filter #107527

Merged
mifu67 merged 4 commits intomasterfrom
mifu67/aci/issue-category-filter-exclude
Feb 5, 2026
Merged

feat(aci): add exclusion to issue category filter #107527
mifu67 merged 4 commits intomasterfrom
mifu67/aci/issue-category-filter-exclude

Conversation

@mifu67
Copy link
Copy Markdown
Contributor

@mifu67 mifu67 commented Feb 3, 2026

We want to allow users to exclude certain issue categories.

@mifu67 mifu67 requested a review from a team as a code owner February 3, 2026 19:03
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 3, 2026
Copy link
Copy Markdown
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

if include:
return bool(value == issue_category or value == issue_category_v2)

return bool(value != issue_category or value != issue_category_v2)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the bots are right about this

Copy link
Copy Markdown
Contributor Author

@mifu67 mifu67 Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, De Morgan's Law 😅

"type": "object",
"properties": {
"value": {"type": "integer", "enum": [*GroupCategory]},
"type": {"type": "boolean"},
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we add bool as a type here?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 maybe naming this notify_on_deescalation would make more sense? (i believe this is the config to determine if users should be notified about the issue on de-escalation as well)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I think I just misunderstood... this is just whether we should include or exclude these issue categories right? So probably we should call it include or exclude?, since that's how we refer to it in code.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include makes sense to me, I will change it!

@mifu67 mifu67 enabled auto-merge (squash) February 5, 2026 19:07
@mifu67 mifu67 merged commit 055226b into master Feb 5, 2026
72 checks passed
@mifu67 mifu67 deleted the mifu67/aci/issue-category-filter-exclude branch February 5, 2026 19:29
jaydgoss pushed a commit that referenced this pull request Feb 12, 2026
We want to allow users to exclude certain issue categories.
dcramer pushed a commit that referenced this pull request Feb 17, 2026
We want to allow users to exclude certain issue categories.
@github-actions github-actions bot locked and limited conversation to collaborators Feb 21, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants