ci: default Prime Agent tickets to Research - #1966
Merged
Merged
Conversation
There was a problem hiding this comment.
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.
Reviewed by Cursor Bugbot for commit e01a7b4. Configure here.
snimu
approved these changes
Sep 2, 2026
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.

Context
Prime Agent work now belongs in the Research team's
Prime Agent: Long-Horizon researchproject, but the GitHub Linear check only recognizes bareENG-*IDs and its examples direct contributors to Engineering.Linear: https://linear.app/primeintellect/issue/RES-1241/default-prime-agent-pull-requests-to-research-linear-tickets
Changes
RES-*ticket references in PR titles, descriptions, branch names, and Linear issue URLs.RES-1234andres-1234in failure guidance.No-Ticket: <short reason>opt-out.Prime Agent: Long-Horizon researchin the workflow and PR template.This validates the Research ticket prefix and updates the default guidance. GitHub Actions cannot verify Linear project membership without a Linear API secret.
Validation
.github/workflows/linear-ticket.ymlas YAML.RES-*tickets, rejectedENG-*tickets, valid opt-outs, malformed opt-outs, and missing-ticket cases with Node.js.git diff --check origin/main...HEAD.Note
Low Risk
Documentation and PR-check regex/message changes only; no runtime product or auth logic.
Overview
Updates the Linear ticket GitHub Action and PR template so Prime Agent work is steered toward Research (
RES-*) tickets and the Prime Agent: Long-Horizon research project, while still accepting legacyENG-*IDs.The workflow regex now matches bare
res-/eng-prefixes (plus existing Linear URLs). Failure text and template comments useRES-1234/res-1234examples and Research project guidance instead of Engineering-only wording.Reviewed by Cursor Bugbot for commit 1101062. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Require 'RES-' ticket prefix for Prime Agent PRs and add opt-out
res-<num>tickets or linear.app links, dropping support foreng-<num>or other prefixesNo-Ticket:line check in the PR body to explicitly bypass the Linear ticket requirementENG-or other non-RESprefixes unless aNo-Ticket:line is present📊 Macroscope summarized e01a7b4. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted
🗂️ Filtered Issues