fix: use \w+ instead of \w{1,} in Label Missing Jira Info description regex#855
Open
nivSwisa1 wants to merge 1 commit into
Open
fix: use \w+ instead of \w{1,} in Label Missing Jira Info description regex#855nivSwisa1 wants to merge 1 commit into
nivSwisa1 wants to merge 1 commit into
Conversation
Equivalent regex, but the braces in \w{1,} trip up js-yaml in the
gitstream pipeline's CM serialization (single-quotes the template, which
the post-process cleanup regex then can't unwrap), causing the rules
engine to see a string instead of a boolean. \w+ is the same pattern
with no `{` `}`.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![orca-security-us[bot]](https://avatars.githubusercontent.com/in/276250?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
OSS Licenses | 0 0 0 0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
![linearb[bot]](https://avatars.githubusercontent.com/in/1658443?s=60&v=4){kind=small}
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.
Summary
\w{1,}with\w+in the description regex example. Same regex semantically; sidesteps a YAML/template serialization issue in the pipeline.The pipeline's
buildCMYamlpost-process regex/'(\{\{[^}]+\}\})'/is meant to strip the single-quotes thatjs-yamladds around any template containing{. With\w{1,}the cleanup fails because[^}]+stops at the inner}of{1,}. The engine then receives a quoted string instead of a template expression, emits "expected a boolean or a numeric value underif", and the check returns"true"(string) instead oftrue(boolean), breaking the missing-jira label rule.Verified against
niv-organization/swell-essentials#194on dev-01: with\w{1,}the description check returned a string + syntax warning; with\w+it round-trips cleanly.Test plan
\w+≡\w{1,}for any string✨ PR Description
Purpose: Fix regex pattern in Jira ticket detection to use standard quantifier syntax for better compatibility and clarity.
Main changes:
\w{1,}to\w+in description regex pattern for matching Jira project keysGenerated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how