Skip to content

fix(ci): soft-pass detailed issues after maintainer retitle - #564

Merged
Wibias merged 2 commits into
lidge-jun:devfrom
Wibias:fix/issue-quality-retitle-softpass
Jul 27, 2026
Merged

fix(ci): soft-pass detailed issues after maintainer retitle#564
Wibias merged 2 commits into
lidge-jun:devfrom
Wibias:fix/issue-quality-retitle-softpass

Conversation

@Wibias

@Wibias Wibias commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Soft-pass no longer requires a [Bug]: / [Feature]: title prefix once issue kind is already established (label / stored kind) and the body has substantial structured content.
  • Prevents the Claude Desktop 3P Auto Mode classifier retries after 64-token Anthropic OAuth outputs #545 false close: maintainer retitle of a detailed non-English report was treated as empty Summary/Reproduction.
  • Same soft-pass path for provider-compatibility when English template headings are absent.

Test plan

Note: live Enforce issue quality loads scripts from the repo default branch (main), so this only takes effect after promotion from dev.

Summary by CodeRabbit

  • Bug Fixes

    • Improved issue validation for feature and bug reports when titles are retitled or use translated headings.
    • Added more flexible validation for provider compatibility reports with substantial structured content.
    • Prevented additional validation errors from appearing when an issue qualifies for a soft pass.
  • Tests

    • Added coverage for retitled and non-English feature and bug reports.

Issue lidge-jun#545 was auto-closed when a maintainer retitle dropped the [Bug]: prefix; soft-pass no longer requires the title prefix once kind is already established and the body has substantial structured content.
@github-actions github-actions Bot added the bug Something isn't working label Jul 27, 2026
@coderabbitai

This comment was marked as outdated.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8cd659c9d1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 583 to 585
const canSoftPass =
!mappedHeadingPresent &&
titleLower.startsWith("[feature]:") &&
hasSubstantialStructuredContent(body);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Require meaningful structure before soft-passing reports

For any issue whose kind is recovered from its existing form label or active bot state, this now accepts an arbitrary body such as ## Notes followed by 40 characters because hasSubstantialStructuredContent requires only one sufficiently long section. The same weakened condition was added to bug and provider reports, and the workflow treats softPass as passing and may reopen a bot-closed issue, so an author can delete every required section and still bypass the quality gate. Require multiple substantive sections or kind-specific evidence rather than one arbitrary heading.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Fixed: hasSubstantialStructuredContent now requires ≥2 rich h2–h4 sections (not one arbitrary heading). Single-section bypass covered by a regression.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/scripts/issue-quality.cjs:
- Around line 695-703: Update the mappedHeadingPresent guard in the soft-pass
logic to also consider provider, version, and endpoint metadata values,
preventing reports with only mapped metadata from soft-passing without required
behavior sections. Add a regression test covering populated mapped metadata with
substantial content but missing current and expected behavior headings.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 45e383ae-0c02-4b68-80a4-5b58d6841adc

📥 Commits

Reviewing files that changed from the base of the PR and between 0fa45cf and 8cd659c.

📒 Files selected for processing (2)
  • .github/scripts/issue-quality.cjs
  • .github/scripts/issue-quality.test.cjs

Comment thread .github/scripts/issue-quality.cjs
Require at least two rich markdown sections before soft-pass, and treat provider metadata headings as mapped so partial English forms cannot bypass Current/Expected behaviour.
@Wibias
Wibias merged commit f348166 into lidge-jun:dev Jul 27, 2026
4 checks passed
@Wibias
Wibias deleted the fix/issue-quality-retitle-softpass branch July 28, 2026 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant