github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[PR #6810] [MERGED] Add workflow to remove 'suspect ai generated' label when 'AI Generated' is added #48571

New Issue
Closed
opened 2026-04-26 10:29:15 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-26 10:29:15 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/6810
Author: @StephenBrown2
Created: 1/28/2026
Status: ✅ Merged
Merged: 1/30/2026
Merged by: @matt-fidd

Base: master ← Head: push-qqusrwprknop

📝 Commits (1)

  • 5f6fc17 Add workflow to remove 'suspect ai generated' label when 'AI Generated' is added

📊 Changes

2 files changed (+31 additions, -0 deletions)

View changed files

➕ .github/workflows/pr-ai-label-cleanup.yml (+25 -0)
➕ upcoming-release-notes/6810.md (+6 -0)

📄 Description

Summary

This PR adds a new GitHub Actions workflow that automatically removes the suspect ai generated label from pull requests when both the AI generated and suspect ai generated labels are present.

What

  • Added new workflow file .github/workflows/pr-ai-label-cleanup.yml
  • Triggers on pull_request_target labeled events
  • Uses the new ubuntu-slim runner (1 vCPU, optimized for lightweight automation tasks)
  • Uses actions/github-script@v8 to call the GitHub API directly

Why

An AI bot automatically adds the suspect ai generated label to PRs it suspects may be AI-generated. When a maintainer reviews the PR and confirms it is AI-generated, they add the AI generated label. At that point, the suspicion label is no longer needed since the PR has been explicitly marked as AI-generated by a maintainer.

How

The workflow triggers on any label addition to a PR. After the label is added, it checks if both labels are present:

  • AI generated (added by maintainers)
  • suspect ai generated (added by AI bot)

If both exist, the suspect ai generated label is removed. This covers two scenarios:

  1. Maintainer adds AI generated to a PR that already has suspect ai generated
  2. AI bot adds suspect ai generated to a PR that a maintainer has already marked as AI generated

Note: This workflow only affects these two specific labels. All other label operations on the PR remain unaffected.

🔄 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/actualbudget/actual/pull/6810 **Author:** [@StephenBrown2](https://github.com/StephenBrown2) **Created:** 1/28/2026 **Status:** ✅ Merged **Merged:** 1/30/2026 **Merged by:** [@matt-fidd](https://github.com/matt-fidd) **Base:** `master` ← **Head:** `push-qqusrwprknop` --- ### 📝 Commits (1) - [`5f6fc17`](https://github.com/actualbudget/actual/commit/5f6fc17f930d2fd2e60992ecb7caddce8ea4cca5) Add workflow to remove 'suspect ai generated' label when 'AI Generated' is added ### 📊 Changes **2 files changed** (+31 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/pr-ai-label-cleanup.yml` (+25 -0) ➕ `upcoming-release-notes/6810.md` (+6 -0) </details> ### 📄 Description ## Summary This PR adds a new GitHub Actions workflow that automatically removes the `suspect ai generated` label from pull requests when both the `AI generated` and `suspect ai generated` labels are present. ## What - Added new workflow file `.github/workflows/pr-ai-label-cleanup.yml` - Triggers on `pull_request_target` labeled events - Uses the new [`ubuntu-slim` runner](https://github.blog/changelog/2026-01-22-1-vcpu-linux-runner-now-generally-available-in-github-actions/) (1 vCPU, optimized for lightweight automation tasks) - Uses `actions/github-script@v8` to call the GitHub API directly ## Why An AI bot automatically adds the `suspect ai generated` label to PRs it suspects may be AI-generated. When a maintainer reviews the PR and confirms it is AI-generated, they add the `AI generated` label. At that point, the suspicion label is no longer needed since the PR has been explicitly marked as AI-generated by a maintainer. ## How The workflow triggers on any label addition to a PR. After the label is added, it checks if **both** labels are present: - `AI generated` (added by maintainers) - `suspect ai generated` (added by AI bot) If both exist, the `suspect ai generated` label is removed. This covers two scenarios: 1. Maintainer adds `AI generated` to a PR that already has `suspect ai generated` 2. AI bot adds `suspect ai generated` to a PR that a maintainer has already marked as `AI generated` **Note:** This workflow only affects these two specific labels. All other label operations on the PR remain unaffected. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-26 10:29:15 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#48571
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?