Skip to content

fix(ci): add pass-through jobs for path-filtered required checks#1207

Open
rjmurillo-bot wants to merge 4 commits intomainfrom
feat/865-autonomous
Open

fix(ci): add pass-through jobs for path-filtered required checks#1207
rjmurillo-bot wants to merge 4 commits intomainfrom
feat/865-autonomous

Conversation

@rjmurillo-bot
Copy link
Collaborator

Pull Request

Summary

Add pass-through jobs to three workflows so that path-filtered required checks emit SUCCESS instead of SKIPPED when irrelevant files change. This unblocks PR merges that do not touch code, memory, or spec paths.

Specification References

Type Reference Description
Issue Fixes #1168 Branch protection treats SKIPPED required checks as failures

Changes

  • ai-pr-quality-gate.yml: Added skip-aggregate job with name "Aggregate Results" that runs when should-run != 'true'
  • ai-spec-validation.yml: Added skip-spec job with name "Validate Spec Coverage" that runs when has-code-changes != 'true'
  • memory-validation.yml: Renamed existing skip-validation job from "Skip validation (no changes)" to "Validate memory citations" to match the required check name. Removed unnecessary checkout step.

Type of Change

  • Bug fix (non-breaking change fixing an issue)
  • New feature (non-breaking change adding functionality)
  • Breaking change (fix or feature causing existing functionality to change)
  • Documentation update
  • Infrastructure/CI change
  • Refactoring (no functional changes)

Testing

  • Tests added/updated
  • Manual testing completed
  • No testing required (documentation only)

YAML syntax validated locally with yaml.safe_load(). Pre-existing test failures confirmed on main (unrelated to this change).

Agent Review

Security Review

  • No security-critical changes in this PR

Other Agent Reviews

  • Architect reviewed design changes
  • Critic validated implementation plan
  • QA verified test coverage

Checklist

  • Code follows project style guidelines
  • Self-review completed
  • Comments added for complex logic
  • Documentation updated (if applicable)
  • No new warnings introduced

Related Issues

Fixes #1168

Branch protection blocks PR merges when required checks report SKIPPED
instead of SUCCESS. This occurs when path filters exclude the real jobs.

Add pass-through jobs with matching check names that emit SUCCESS when
the path filter skips the real job. Affected checks:
- Aggregate Results (ai-pr-quality-gate.yml)
- Validate Spec Coverage (ai-spec-validation.yml)
- Validate memory citations (memory-validation.yml)

Fixes #1168

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@chatgpt-codex-connector
Copy link

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@github-actions github-actions bot added enhancement New feature or request area-workflows GitHub Actions workflows github-actions GitHub Actions workflow updates labels Feb 20, 2026
@rjmurillo-bot rjmurillo-bot enabled auto-merge (squash) February 20, 2026 01:22
@github-actions
Copy link
Contributor

PR Validation Report

Caution

Status: FAIL

Description Validation

Check Status
Description matches diff FAIL

QA Validation

Check Status
Code changes detected True
QA report exists false

⚠️ Blocking Issues

  • PR description does not match actual changes

⚡ Warnings

  • QA report not found for code changes (recommended before merge)

Powered by PR Validation workflow

@coderabbitai coderabbitai bot requested a review from rjmurillo February 20, 2026 01:23
@coderabbitai coderabbitai bot added area-infrastructure Build, CI/CD, configuration bug Something isn't working labels Feb 20, 2026
@coderabbitai
Copy link

coderabbitai bot commented Feb 20, 2026

Caution

Review failed

Failed to post review comments

📝 Walkthrough

Walkthrough

Adds test cases for path normalization handling of Markdown bold markers and a new episodic memory record. The tests validate that normalize_path strips Markdown formatting (** delimiters) from filenames and that extract_mentioned_files correctly deduplicates bold-formatted filenames in list items.

Changes

Cohort / File(s) Summary
Test additions
tests/test_validation_pr_description.py
Three new test cases: normalize_path strips leading and surrounding Markdown bold markers (**foo.yml and **foo.yml**foo.yml); extract_mentioned_files correctly deduplicates bold filenames in list items.
Episode memory
.agents/memory/episodes/episode-2026-02-25-session-1.json
New episodic memory file with session metadata, including 3 commits recorded; outcome marked as partial; no errors, duration, or file change metrics recorded.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Out of Scope Changes check ⚠️ Warning PR contains out-of-scope changes: .agents/memory/episodes/episode-2026-02-25-session-1.json is unrelated to fixing branch protection SKIPPED issues and should not be included. Remove the episode memory JSON file from this PR as it is not related to the #1168 fix. This file belongs in a separate commit/PR.
Docstring Coverage ⚠️ Warning Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed Title follows conventional commit format with 'fix(ci)' prefix and clearly describes adding pass-through jobs for path-filtered required checks.
Description check ✅ Passed Description directly relates to the changeset, explaining the purpose of pass-through jobs and detailing which workflows were modified and how.
Linked Issues check ✅ Passed Code changes fully address issue #1168 requirements: added pass-through jobs to three workflows (ai-pr-quality-gate.yml, ai-spec-validation.yml, memory-validation.yml) that run when path filters skip real jobs, converting SKIPPED to SUCCESS.

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

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/865-autonomous

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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

…atching

The list item regex pattern captured leading `**` from bold-formatted
filenames in list items (e.g. `- **file.yml**: description`). This
caused false CRITICAL issues when the extracted `**file.yml` did not
suffix-match the actual diff path `.github/workflows/file.yml`.

Strip `*` characters in normalize_path so both the bold pattern and
list item pattern produce clean filenames for matching.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions github-actions bot added the automation Automated workflows and processes label Feb 20, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 20, 2026

✅ Pass: Memory Validation

No memories with citations found.


📊 Validation Details
  • Total memories checked: 0
  • Valid: 0
  • Stale: 0

@github-actions github-actions bot added the infrastructure-failure CI infrastructure failure (Copilot CLI auth, rate limits, etc.) label Feb 21, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 21, 2026

AI Quality Gate Review

Tip

Final Verdict: PASS

Walkthrough

This PR was reviewed by six AI agents in parallel, analyzing different aspects of the changes:

  • Security Agent: Scans for vulnerabilities, secrets exposure, and security anti-patterns
  • QA Agent: Evaluates test coverage, error handling, and code quality
  • Analyst Agent: Assesses code quality, impact analysis, and maintainability
  • Architect Agent: Reviews design patterns, system boundaries, and architectural concerns
  • DevOps Agent: Evaluates CI/CD, build pipelines, and infrastructure changes
  • Roadmap Agent: Assesses strategic alignment, feature scope, and user value

Review Summary

Agent Verdict Category Status
Security PASS N/A
QA PASS N/A
Analyst PASS N/A
Architect PASS N/A
DevOps PASS N/A
Roadmap PASS N/A

💡 Quick Access: Click on individual agent jobs (e.g., "🔒 security Review", "🧪 qa Review") in the workflow run to see detailed findings and step summaries.

Security Review Details

Security Review: PR #1207

PR Type Classification

File Category Security Scrutiny
.agents/memory/episodes/episode-2026-02-25-session-1.json CONFIG Schema only
.agents/sessions/2026-02-25-session-1.json CONFIG Schema only
tests/test_validation_pr_description.py CODE Full review

Findings

Severity Category Finding Location CWE
None - No vulnerabilities identified - -

Analysis Summary

Session/Episode JSON Files (CONFIG)

  • Contains only metadata: timestamps, branch names, commit SHAs, compliance checklists
  • No secrets, credentials, or sensitive data exposed
  • Internal session tracking data only

Test File (CODE)

  • Adds 4 new test methods for path normalization (bold markers, backticks)
  • Test cases use literal strings as fixtures (foo.yml, workflow.yml)
  • No user input processing, no external calls in added code
  • All assertions are deterministic string comparisons
  • No injection vectors (tests mock subprocess calls properly)

Recommendations

None required. Changes are low-risk additions to existing test coverage.

Verdict

VERDICT: PASS
MESSAGE: Session metadata (CONFIG) contains no secrets. Test additions use safe literal fixtures with no injection surface.
QA Review Details

Let me check where the skip-aggregate job is in this workflow:

Now I have a complete picture. Let me view the test file changes to verify test quality:

Now I have a complete picture of this PR. Let me provide the QA verdict:


QA Review Verdict

VERDICT: PASS
MESSAGE: WORKFLOW changes with proper pass-through jobs for required checks; tests added for existing functionality.

PR TYPE: MIXED (WORKFLOW + CONFIG)
FILES:
  - WORKFLOW: .github/workflows/ai-pr-quality-gate.yml (aggregate-skip job), .github/workflows/ai-spec-validation.yml (validate-spec-skip job), .github/workflows/memory-validation.yml (skip-validation job)
  - CONFIG: .agents/memory/episodes/*.json, .agents/sessions/*.json (session metadata)
  - TEST: tests/test_validation_pr_description.py (new test cases for existing functions)

EVIDENCE:
- Tests found: 4 new tests added to test_validation_pr_description.py for existing normalize_path and extract_mentioned_files functions
- Test execution: PASS (4486 passed, 3 skipped, 5 warnings in 29.28s)
- Edge cases: N/A (workflow changes, not user-facing code)
- Error handling: N/A (pass-through jobs emit SUCCESS unconditionally by design)
- Blocking issues: 0

Test Coverage Assessment

Area Status Evidence Files Checked
Unit tests Adequate 4 new tests: test_strips_markdown_bold_markers, test_strips_surrounding_bold_markers, test_bold_in_list_item_deduplicates, plus backtick tests tests/test_validation_pr_description.py:45-49, 132-137
Workflow changes N/A Pass-through jobs have no logic to test - they emit static SUCCESS .github/workflows/*.yml
Session files N/A Metadata files do not require tests .agents/sessions/*.json

Quality Concerns

Severity Issue Location Evidence Required Fix
None - - - -

Regression Risk Assessment

  • Risk Level: Low
  • Affected Components: GitHub Actions workflow execution paths for non-code PRs
  • Breaking Changes: None - these are additive pass-through jobs
  • Required Testing: Manual verification that non-code PRs merge without SKIPPED check failures

Verification of PR Claims

Claim Verified Evidence
ai-pr-quality-gate.yml: aggregate-skip job Lines 470-480: aggregate-skip with name "Aggregate Results"
ai-spec-validation.yml: validate-spec-skip job Lines 92-102: validate-spec-skip with name "Validate Spec Coverage"
memory-validation.yml: skip-validation renamed Lines 171-182: skip-validation with name "Validate memory citations"

Pattern Compliance

The pass-through job pattern is consistent across all three workflows:

  1. Same job naming convention matches the required check name
  2. Conditional execution (if: ... != 'true') ensures mutual exclusivity
  3. Single echo step minimizes execution time
Analyst Review Details

I now have enough information to provide the analysis.


Analyst Review: PR #1207

Code Quality Score

Criterion Score (1-5) Notes
Readability 5 Clear job names, well-documented comments referencing issue #1168
Maintainability 5 Pass-through pattern is consistent across all three workflows
Consistency 5 Follows established dorny/paths-filter pattern already in repo
Simplicity 5 Minimal change: add/rename jobs with descriptive echo statements

Overall: 5/5

Impact Assessment

  • Scope: Module-wide (CI workflows only)
  • Risk Level: Low
  • Affected Components:
    • .github/workflows/ai-pr-quality-gate.yml (aggregate-skip job)
    • .github/workflows/ai-spec-validation.yml (validate-spec-skip job)
    • .github/workflows/memory-validation.yml (skip-validation renamed)

Findings

Priority Category Finding Location
Low Documentation Session files included in PR but should commit separately .agents/sessions/*.json, .agents/memory/episodes/*.json
Low Testing Test additions for normalize_path are valid and independent tests/test_validation_pr_description.py:45-54,132-137

Analysis Details

Workflow Changes (Verified in current codebase):

  1. ai-pr-quality-gate.yml: aggregate-skip job exists at lines 473-480 with correct name "Aggregate Results" and condition needs.check-changes.outputs.should-run != 'true'

  2. ai-spec-validation.yml: validate-spec-skip job exists at lines 92-102 with correct name "Validate Spec Coverage" and condition needs.check-paths.outputs.has-code-changes != 'true'

  3. memory-validation.yml: skip-validation job exists at lines 174-182 with name "Validate memory citations" matching the real validation job name (line 45)

Pattern Validation:

Test Changes:

  • 4 new test methods in TestNormalizePath and TestExtractMentionedFiles classes
  • Tests are independent and cover markdown bold marker stripping functionality
  • Tests appear related to merge conflict resolution (keeping both branches' additions)

Recommendations

  1. Session log files (.agents/sessions/, .agents/memory/episodes/) are typically excluded from feature PRs but inclusion is acceptable for merge conflict resolution commits.

Verdict

VERDICT: PASS
MESSAGE: CI pass-through jobs correctly satisfy branch protection requirements for path-filtered workflows. Pattern is consistent, minimal, and well-documented.
Architect Review Details

The file only has 803 lines. Let me check around line 60-140 for the skip-aggregate job mentioned in the PR description.

I need to find the skip-aggregate job mentioned in the PR. Let me search for it:

Now I have enough context. Let me check the test file changes:

I have gathered sufficient information to complete the architectural review.


Design Quality Assessment

Aspect Rating (1-5) Notes
Pattern Adherence 5 Follows established pass-through job pattern consistently across 3 workflows
Boundary Respect 5 Changes confined to CI workflow YAML and related test files
Coupling 5 Jobs use existing needs dependencies; no new coupling introduced
Cohesion 5 Each pass-through job has single purpose: emit SUCCESS for branch protection
Extensibility 4 Pattern is repeatable for other workflows with required checks

Overall Design Score: 5/5


Architectural Concerns

Severity Concern Location Recommendation
None No architectural concerns identified N/A N/A

Breaking Change Assessment

  • Breaking Changes: No
  • Impact Scope: None
  • Migration Required: No
  • Migration Path: N/A

Technical Debt Analysis

  • Debt Added: None
  • Debt Reduced: Low (removes friction from PR merge workflow)
  • Net Impact: Improved

ADR Assessment

  • ADR Required: No
  • Decisions Identified: Pass-through job pattern for branch protection compatibility
  • Existing ADR: ADR-026-pr-automation-concurrency-and-safety.md (covers workflow concurrency, not this specific pattern)
  • Recommendation: N/A. This is a tactical fix for GitHub branch protection behavior, not a strategic architectural decision. The pattern is documented inline via comments referencing issue fix: Branch protection treats SKIPPED required checks as failures #1168.

Recommendations

  1. Pattern is sound and consistent across all 3 workflows. Comments cite issue fix: Branch protection treats SKIPPED required checks as failures #1168 for traceability.
  2. Test additions for normalize_path are unrelated to CI changes but are valid merge conflict resolution artifacts.
  3. Session log and episode files follow established schema.

Verdict

VERDICT: PASS
MESSAGE: Pass-through jobs follow established CI patterns. No architectural concerns. Changes are confined to workflow YAML with inline documentation.
DevOps Review Details

Let me find the pass-through job for the quality gate:

The file view shows the ai-pr-quality-gate.yml ends at line 803. Let me look at the git diff for this PR directly to see what was actually changed:

Based on my review of the workflow files in the current repository, I have enough information to provide the DevOps review. The PR description indicates changes to add pass-through jobs to handle path-filtered required checks. Let me analyze what I've seen:


DevOps Review: PR #1207 - Add Pass-Through Jobs for Path-Filtered Required Checks

PR Scope Detection

Category Files Changed Review Scope
WORKFLOW ai-pr-quality-gate.yml, ai-spec-validation.yml, memory-validation.yml Full CI/CD review
SESSION .agents/sessions/*.json, .agents/memory/episodes/*.json None required
TEST tests/test_validation_pr_description.py Build impact only

Pipeline Impact Assessment

Area Impact Notes
Build None No build script changes
Test Low Test additions are additive
Deploy None No deployment changes
Cost Low Skip jobs use ubuntu-24.04-arm with minimal steps

CI/CD Quality Checks

Check Status Location
YAML syntax valid All workflow files viewed parse correctly
Actions pinned actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36
Secrets secure Secrets referenced via ${{ secrets.* }} only
Permissions minimal contents: read, pull-requests: write
Shell scripts robust Echo-only in skip jobs

Design Review

The pass-through job pattern is correctly implemented:

ai-spec-validation.yml (lines 92-102):

  • Job validate-spec-skip has name Validate Spec Coverage (matches real job)
  • Condition: if: always() && needs.check-paths.result == 'success' && needs.check-paths.outputs.has-code-changes != 'true'
  • Mutually exclusive with validate-spec job (one runs when has-code-changes == 'true', skip runs otherwise)
  • [PASS] Correct implementation

memory-validation.yml (lines 171-182):

  • Job skip-validation renamed to Validate memory citations (matches real job name)
  • Condition: if: needs.check-paths.outputs.memories-changed != 'true' && needs.check-paths.outputs.code-changed != 'true'
  • Mutually exclusive with validate-memories job
  • [PASS] Correct implementation, checkout step removed (unnecessary for echo-only job)

ai-pr-quality-gate.yml:

  • PR description mentions adding skip-aggregate job with name Aggregate Results
  • Current file view shows 803 lines with aggregation at end
  • Pass-through pattern should run when should-run != 'true'

Findings

Severity Category Finding Location Fix
Low Cost Skip jobs use ubuntu-24.04-arm which is optimal All skip jobs None needed
Info Documentation Issue #1168 correctly referenced in comments All skip jobs None needed

Template Assessment

  • PR Template: Adequate - all sections completed
  • Issue Templates: Not affected
  • Template Issues: None

Automation Opportunities

Opportunity Type Benefit Effort
None identified - - -

The pass-through job pattern is a known solution for GitHub branch protection's SKIPPED status limitation. No new automation needed.

Recommendations

  1. None - implementation follows established patterns in the repository

Notes on Expected Patterns

The following patterns are normal and acceptable:

  • ubuntu-24.04-arm runner: Per ADR-025 for cost optimization
  • if: always() && needs.*.result == 'success': Required to handle transitive skip chains
  • Echo-only skip jobs: Minimal compute for pass-through functionality

VERDICT: PASS
MESSAGE: Pass-through jobs correctly implement GitHub required check bypass pattern. Actions pinned, permissions minimal, mutually exclusive conditions prevent both real and skip jobs from running simultaneously.
Roadmap Review Details

Strategic Alignment Assessment

Criterion Rating Notes
Aligns with project goals High Removes friction for documentation-only and config PRs
Priority appropriate High Blocking bug in merge workflow - P0 priority
User value clear High Developers cannot merge PRs when SKIPPED status blocks branch protection
Investment justified High Minimal YAML changes with high productivity impact

Feature Completeness

  • Scope Assessment: Right-sized
  • Ship Ready: Yes
  • MVP Complete: Yes
  • Enhancement Opportunities: None identified. The pattern is consistent across all three workflows.

Impact Analysis

Dimension Assessment Notes
User Value High Unblocks developer workflow for documentation, memory, and non-code PRs
Business Impact Medium Reduces merge friction, improves developer velocity
Technical Leverage Medium Establishes pattern for future path-filtered workflows
Competitive Position Neutral Internal infrastructure fix

RICE Score (Reference)

Factor Value Rationale
Reach All contributors Every PR without code changes is affected
Impact 3 (massive) Blocking bug preventing merges
Confidence 100% Issue #1168 documents exact failure mode
Effort 0.1 person-days Three small YAML edits
Score Very High Clear ROI for minimal investment

KANO Classification

Must-Be (Basic Expectation): Branch protection should not block PRs incorrectly. Users expect the merge button to work when checks pass. This is a defect fix, not a feature.

Concerns

Priority Concern Recommendation
Low Duplicate job names could confuse workflow monitoring Acceptable tradeoff; required check name must match
Low Session log and episode artifacts included in PR Standard practice per session protocol

Recommendations

  1. Merge this PR promptly. Blocking merges on documentation-only PRs creates unnecessary friction.
  2. Consider documenting this pass-through pattern in a workflow authoring guide for consistency.

Verdict

VERDICT: PASS
MESSAGE: Infrastructure fix removes merge friction. Minimal effort, high impact, addresses documented bug #1168.

Run Details
Property Value
Run ID 22421291024
Triggered by pull_request on 1207/merge
Commit e51e10274c8cc58cd5ab0086070b949152692287

Powered by AI Quality Gate workflow

@coderabbitai coderabbitai bot added the agent-devops CI/CD pipeline agent label Feb 21, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (2)
.github/workflows/ai-pr-quality-gate.yml (1)

408-416: Add timeout-minutes for consistency.

The memory-validation.yml skip job has timeout-minutes: 1. This skip-aggregate job should match. Without a timeout, a hypothetical hang consumes the 360-minute default.

🔧 Add timeout
   skip-aggregate:
     name: Aggregate Results
     runs-on: ubuntu-24.04-arm
+    timeout-minutes: 1
     needs: check-changes
     if: always() && needs.check-changes.outputs.should-run != 'true'
     steps:
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ai-pr-quality-gate.yml around lines 408 - 416, The
skip-aggregate job (job name "skip-aggregate", workflow job id skip-aggregate)
lacks a timeout and can hang for the default 360 minutes; add a timeout-minutes:
1 entry to the job definition (same level as runs-on/needs/if) so the
pass-through Aggregate Results job times out quickly like the
memory-validation.yml skip job.
.github/workflows/ai-spec-validation.yml (1)

92-100: Add timeout-minutes for consistency.

Same as the ai-pr-quality-gate skip job: memory-validation.yml sets timeout-minutes: 1 on its skip job. Match that pattern here.

🔧 Add timeout
   skip-spec:
     name: Validate Spec Coverage
     runs-on: ubuntu-24.04-arm
+    timeout-minutes: 1
     needs: check-paths
     if: needs.check-paths.outputs.has-code-changes != 'true'
     steps:
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ai-spec-validation.yml around lines 92 - 100, The
skip-spec job (named "Validate Spec Coverage" with job id skip-spec) is missing
a timeout and should match the pattern used elsewhere; add a timeout-minutes: 1
property to the skip-spec job definition so the job has the same short timeout
as the other skip jobs (e.g., as in memory-validation.yml), ensuring the timeout
key is placed at the same indentation level as runs-on and needs within the
skip-spec job block.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/workflows/ai-pr-quality-gate.yml:
- Around line 408-416: The skip-aggregate job (job name "skip-aggregate",
workflow job id skip-aggregate) lacks a timeout and can hang for the default 360
minutes; add a timeout-minutes: 1 entry to the job definition (same level as
runs-on/needs/if) so the pass-through Aggregate Results job times out quickly
like the memory-validation.yml skip job.

In @.github/workflows/ai-spec-validation.yml:
- Around line 92-100: The skip-spec job (named "Validate Spec Coverage" with job
id skip-spec) is missing a timeout and should match the pattern used elsewhere;
add a timeout-minutes: 1 property to the skip-spec job definition so the job has
the same short timeout as the other skip jobs (e.g., as in
memory-validation.yml), ensuring the timeout key is placed at the same
indentation level as runs-on and needs within the skip-spec job block.

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 21, 2026
@rjmurillo rjmurillo closed this Feb 21, 2026
auto-merge was automatically disabled February 21, 2026 06:12

Pull request was closed

@rjmurillo rjmurillo reopened this Feb 21, 2026
@rjmurillo rjmurillo enabled auto-merge (squash) February 21, 2026 06:37
rjmurillo-bot and others added 2 commits February 25, 2026 15:50
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Contributor

Session Protocol Compliance Report

Tip

Overall Verdict: PASS

All session protocol requirements satisfied.

What is Session Protocol?

Session logs document agent work sessions and must comply with RFC 2119 requirements:

  • MUST: Required for compliance (blocking failures)
  • SHOULD: Recommended practices (warnings)
  • MAY: Optional enhancements

See .agents/SESSION-PROTOCOL.md for full specification.

Compliance Summary

Session File Verdict MUST Failures
sessions-2026-02-25-session-1.md ✅ COMPLIANT 0

Detailed Validation Results

Click each session to see the complete validation report with specific requirement failures.

📄 sessions-2026-02-25-session-1

=== Session Validation ===
File: /home/runner/work/ai-agents/ai-agents/.agents/sessions/2026-02-25-session-1.json

[PASS] Session log is valid


✨ Zero-Token Validation

This validation uses deterministic script analysis instead of AI:

  • Zero tokens consumed (previously 300K-900K per debug cycle)
  • Instant feedback - see exact failures in this summary
  • No artifact downloads needed to diagnose issues
  • 10x-100x faster debugging

Powered by validate_session_json.py

📊 Run Details
Property Value
Run ID 22421290995
Files Checked 1
Validation Method Deterministic script analysis

Powered by Session Protocol Validator workflow

@rjmurillo
Copy link
Owner

Review Triage Required

Note

Priority: NORMAL - Human approval required before bot responds

Review Summary

Source Reviews Comments
Human 0 0
Bot 2 0

Next Steps

  1. Review human feedback above
  2. Address any CHANGES_REQUESTED from human reviewers
  3. Add triage:approved label when ready for bot to respond to review comments

Powered by PR Maintenance workflow - Add triage:approved label

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

Labels

agent-devops CI/CD pipeline agent area-infrastructure Build, CI/CD, configuration area-workflows GitHub Actions workflows automation Automated workflows and processes bug Something isn't working enhancement New feature or request github-actions GitHub Actions workflow updates infrastructure-failure CI infrastructure failure (Copilot CLI auth, rate limits, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: Branch protection treats SKIPPED required checks as failures

2 participants