Repository navigation
accept engineering and research tickets in the contribution gate - #2124
Merged
Merged
Conversation
sethkarten
reviewed
Sep 8, 2026
snimu
pushed a commit
that referenced
this pull request
Sep 10, 2026
* fix(ci): accept engineering and research Linear tickets * fix(ci): clarify the Research ticket project fixes #2124 * fix(coding-agent): include the lazy Bedrock provider in CLI bundles Fixes ENG-6006 * fix(ci): clarify Prime Agent board routing fixes #2124 * fix(coding-agent): preserve structured Bedrock logs fixes #2134 * test(coding-agent): await Bedrock fixture daemon shutdown fixes #2134 * fix(ci): require complete Linear ticket identifiers * test(coding-agent): guarantee Bedrock fixture cleanup * test(coding-agent): allow context before Bedrock prompts * test(coding-agent): allow context before literal prompts * fix(ci): isolate Ubuntu package sources
snimu
pushed a commit
that referenced
this pull request
Sep 10, 2026
* fix(ci): accept engineering and research Linear tickets * fix(ci): clarify the Research ticket project fixes #2124 * fix(coding-agent): preserve reasoning in auxiliary calls Refs ENG-6010 and discussions #1482 and #2081. * fix(ci): clarify Prime Agent board routing fixes #2124 * fix(coding-agent): reserve refinement reasoning output budget Remove fixed output caps when reasoning is enabled and reserve prompt context within the model limit. Keep truncation failures bounded without retrying. fixes #2130 * fix: preserve refinement context and valid thinking budgets Estimate refinement tokens and shorten only older trajectory content when space is tight. Enforce valid minimum thinking budgets for budget-based Claude requests. fixes #2130 * fix(ci): isolate Ubuntu package sources (cherry picked from commit 7656902) * test(coding-agent): allow context before literal prompts (cherry picked from commit 59e9714) * fix(coding-agent): bound dense refinement context (fixes #2130)
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
2 participants
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.
npm run check.no-ticket: contribution workflow maintenance.
Note
Low Risk
Only GitHub workflow regex and contributor template text change; no application or security logic is affected.
Overview
The PR contribution gate now treats Engineering (
ENG-*) tickets the same as Research (RES-*) when checking PR titles, descriptions, branch names, andlinear.appissue links.The PR template Context section is updated so contributors link either an ENG ticket on the Prime Agent V1 board or a RES ticket on the Prime Agent: Long-Horizon board (or use
No-Ticket:when appropriate). The linear-ticket workflow regex and failure text match that split, with examples for both ticket prefixes.Reviewed by Cursor Bugbot for commit 8f8d8d9. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Accept Engineering (
ENG) tickets in contribution gate alongside Research (RES)Changes since #2124 opened
linear-ticket.ymlGitHub workflow to clarify that Prime Agent tickets may reference either the Engineering team or the Research team with the Prime Agent: Long-Horizon research project [a41e7cb]Engineering (ENG)team with thePrime Agent V1board, and capabilities/research issues should reference theResearch (RES)team with thePrime Agent: Long-Horizonboard [8f8d8d9]📊 Macroscope summarized a41e7cb. 1 file reviewed, 1 issue evaluated, 1 issue filtered, 0 comments posted
🗂️ Filtered Issues
.github/workflows/linear-ticket.yml — 0 comments posted, 1 evaluated, 1 filtered
\d+, so a PR body containing a non-ticket string such ashttps://linear.app/team/issue/ENG-123not-a-ticketsatisfies the gate. Unlike the bare-ID alternative, this permits a malformed Engineering reference to bypass the required-ticket check. [ Out of scope (post-validation triage) ]