Skip to content

feat: implement issue #629 — Compliance: non-stub-feature-ideation.yml - #805

Merged
don-petry merged 7 commits into
mainfrom
dev-lead/issue-629-20260619-1533
Jun 19, 2026
Merged

don-petry merged 7 commits into
mainfrom
dev-lead/issue-629-20260619-1533

Conversation

@don-petry

@don-petry don-petry commented Jun 19, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #629

Implemented by dev-lead agent. Please review.

Summary by CodeRabbit

Release Notes

  • Tests

    • Added comprehensive regression test suite validating Feature Ideation workflow compliance, configuration correctness, trigger conditions for newly created discussion items, and reusable workflow version pinning standards.
  • Chores

    • Updated Feature Ideation workflow configuration with refined conditional guards for discussion-triggered automation and refreshed reusable workflow service references.
    • Extended linting configuration to properly include and validate new workflow test files.

@don-petry
don-petry requested a review from a team as a code owner June 19, 2026 15:39
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Jun 19, 2026 •

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The feature-ideation.yml workflow gains a job-level if: guard limiting discussion: created triggers to the Ideas category from non-bot users, bumps the reusable workflow uses: reference to a new v1-pinned SHA, and wires with.target_discussion from the created Discussion number. A new bats test file enforces these constraints in CI.

Changes

Feature Ideation Compliance Update

Layer / File(s) Summary
Workflow trigger guard, v1 pin, and target_discussion wiring
.github/workflows/feature-ideation.yml
Expands documentation comments and adoption guidance, updates the focus_area and dry_run input descriptions, adds a jobs.ideate.if conditional to restrict discussion-triggered runs to Ideas-category non-bot creations, bumps the uses: reference to the v1-pinned SHA, and adds with.target_discussion sourced from github.event.discussion.number.
Bats regression tests and lint CI registration
tests/test_feature_ideation.bats, .github/workflows/lint.yml
Adds a new bats test suite asserting the workflow file exists, references the correct reusable workflow path, is pinned to the v1 SHA with a # v1 annotation, and is not pinned to the superseded v2 SHA. Registers the test file in the lint.yml bats job's file list with correct line continuation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

Possibly related PRs

Suggested labels

needs-human-review

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the implementation of issue #629 regarding compliance with the feature-ideation workflow standards, directly reflecting the main changes in the PR.
Linked Issues check ✅ Passed The PR successfully addresses all coding requirements from issue #629: updating feature-ideation.yml to pin the reusable workflow to @v1, adding compliance validation tests, and ensuring alignment with organizational CI standards.
Out of Scope Changes check ✅ Passed All changes are scoped to compliance remediation: workflow updates align with issue #629 requirements, test additions validate the compliance fix, and no unrelated modifications are present.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev-lead/issue-629-20260619-1533

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist 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.

Code Review

This pull request introduces a new BATS test suite (tests/test_feature_ideation.bats) to enforce compliance for the .github/workflows/feature-ideation.yml workflow, ensuring it correctly pins the reusable workflow to the v1 SHA. The feedback suggests a robustness improvement in the test checking for the superseded v2 SHA: explicitly verifying the file's existence before running a negated grep command to avoid false positives from execution errors.

Comment thread tests/test_feature_ideation.bats
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — review-changes (applied)

Changes committed and pushed.

@don-petry
don-petry enabled auto-merge (squash) June 19, 2026 15:44
@don-petry
don-petry disabled auto-merge June 19, 2026 15:57
coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 19, 2026
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-bot-comment (applied)

Changes committed and pushed.

@don-petry
don-petry disabled auto-merge June 19, 2026 16:04
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — waiting on PR blockers (intent: review-changes)

PR: #805
No changes were committed, but the PR still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews). The retry cron will re-attempt automatically. Next attempt after: 2026-06-19T16:35:44Z

@don-petry

Copy link
Copy Markdown
Collaborator Author

Note

@don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically.
Next attempt after: 2026-06-19T16:35:44Z

@don-petry
don-petry enabled auto-merge (squash) June 19, 2026 16:05
@donpetry-bot

Copy link
Copy Markdown
Contributor

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-19T17:13:28Z.

@donpetry-bot donpetry-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: f9595ab69ef2290e4ea0888006c2d2ce3947006b
Review mode: triage-approved (single reviewer)

Summary

Compliance fix for #629: syncs .github/workflows/feature-ideation.yml to the canonical org stub, restoring the @v1 reusable pin (897e4dede… # v1) in place of the superseded v2 SHA. Also adds a bats regression test guarding the v1 pin and registers it in lint.yml. The local stub is byte-identical to the upstream source of truth except for the intended per-repo project_context / sources_file customization; the uses: line, discussion: created trigger, ideas-category/non-bot if-guard, and target_discussion input all match the standard exactly.

Linked issue analysis

Closes #629 (compliance finding: feature-ideation.yml not pinned to @v1). Substantively addressed — the reusable is now pinned to the canonical v1 SHA matching standards/workflows/feature-ideation.yml, and the new test (tests/test_feature_ideation.bats) asserts the v1 pin + # v1 annotation and forbids the old v2 SHA, preventing re-filing.

Findings

No blocking findings.

  • Verified new SHA 897e4dede… is a real commit in petry-projects/.github and matches the canonical source-of-truth stub's uses: line (annotated # v1).
  • discussion: created trigger is part of the vetted org standard and carries an if-guard (category.slug == 'ideas' && user.type != 'Bot'); permissions are scoped and documented. No GitHub Actions security smell introduced by this PR.
  • Diff of local stub vs canonical shows only the expected project_context and sources_file customization; all protected lines match.
  • MCP run_secret_scanning was not available/permitted in this run; relied on the passing gitleaks CI check. Changed files (workflow YAML + bats) contain no secret material — only git SHAs and a reference to the secret name CLAUDE_CODE_OAUTH_TOKEN, no values.

CI status

All required checks green: Lint, shellcheck/ShellCheck, bats, unit-tests, CodeQL (actions+python), Secret scan (gitleaks), agent-shield/AgentShield, SonarCloud, validate-agent-profiles, gh-aw-compile, holdout-guard, etc. The two CANCELLED entries (dev-lead / dispatch, dev-lead / ci-relay) are the bot's own superseded dispatch jobs, not test failures. mergeStateStatus BLOCKED is solely due to REVIEW_REQUIRED, which this approval addresses.


Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.

@don-petry
don-petry disabled auto-merge June 19, 2026 16:35
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry
don-petry enabled auto-merge (squash) June 19, 2026 16:35

@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 `@tests/test_feature_ideation.bats`:
- Around line 36-38: The grep command in the test "feature-ideation.yml uses:
line is annotated # v1" interpolates the unescaped ${REUSABLE} variable into an
Extended Regular Expression pattern, which causes special regex characters like
dots to be interpreted as wildcards instead of literal characters. This allows
malformed uses: values to pass the test. Escape the special regex characters in
${REUSABLE} before using it in the grep pattern, particularly dots and other
metacharacters that could appear in paths. Consider using sed to escape these
characters or switching to grep -F for literal string matching instead of ERE
pattern matching.
🪄 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 85a4495d-3ffc-4be9-b5d8-b7fe26ba4a2c

📥 Commits

Reviewing files that changed from the base of the PR and between 0fb2ea6 and 0769db0.

📒 Files selected for processing (3)
  • .github/workflows/feature-ideation.yml
  • .github/workflows/lint.yml
  • tests/test_feature_ideation.bats

Comment thread tests/test_feature_ideation.bats
@don-petry
don-petry disabled auto-merge June 19, 2026 16:50
@don-petry
don-petry enabled auto-merge (squash) June 19, 2026 16:51
@sonarqubecloud

Copy link
Copy Markdown

@don-petry
don-petry merged commit f1ac0ed into main Jun 19, 2026
31 of 43 checks passed
@don-petry
don-petry deleted the dev-lead/issue-629-20260619-1533 branch June 19, 2026 16:58
@donpetry-bot

Copy link
Copy Markdown
Contributor

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-19T18:03:21Z.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Compliance: non-stub-feature-ideation.yml

2 participants