Skip to content

ci: add placeholder required status gate#5

Merged
WomB0ComB0 merged 1 commit into
mainfrom
feat/ci-governance-adoption
Apr 17, 2026
Merged

ci: add placeholder required status gate#5
WomB0ComB0 merged 1 commit into
mainfrom
feat/ci-governance-adoption

Conversation

@WomB0ComB0
Copy link
Copy Markdown
Member

Summary

Adds a minimal required.yml workflow that always emits a green required status-check context — the context matched by the org ruleset default-branch-baseline (id 15191038, currently evaluate mode).

This is a placeholder. Before flipping the ruleset to active, either:

  • Add needs: on real CI jobs in this repo, or
  • Replace with a call to a reusable workflow in resq-software/.github once the matching language-ci.yml exists.

Context: resq-software/.github#12 defines the full reusable CI suite. This repo'''s lang is deferred in that PR and will get a proper workflow in a follow-up.

Satisfies the `required` status-check context in org ruleset
`default-branch-baseline` (id 15191038, currently evaluate mode).

Placeholder: this job always passes. Before the ruleset flips to
active, harden it with `needs:` on real language-CI jobs or
replace with a call to a reusable workflow from
resq-software/.github once the matching lang-ci.yml exists.
@gemini-code-assist
Copy link
Copy Markdown

Note

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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 17, 2026

Warning

Rate limit exceeded

@WomB0ComB0 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 37 minutes and 11 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 37 minutes and 11 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 16d22838-04ef-41b5-84dd-23a8b984aac4

📥 Commits

Reviewing files that changed from the base of the PR and between 1d7f5ef and 246736b.

📒 Files selected for processing (1)
  • .github/workflows/required.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/ci-governance-adoption

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.

@WomB0ComB0 WomB0ComB0 merged commit c263ff8 into main Apr 17, 2026
17 checks passed
@WomB0ComB0 WomB0ComB0 deleted the feat/ci-governance-adoption branch April 17, 2026 10:14
WomB0ComB0 added a commit that referenced this pull request May 4, 2026
Adds the docs-specific CI governance workflows on top of the placeholder
required gate (#5).

New workflows
- workflows/lychee.yml      — link checker (markdown + mdx + docs.json)
- workflows/i18n-parity.yml — informational locale parity report
- workflows/labeler.yml     — auto-label PRs by touched paths
- workflows/stale.yml       — close abandoned issues/PRs
- labeler.yml               — labeler action config

Hardened
- workflows/required.yml — adds mintlify broken-link job to needs:, so
  the aggregate \`required\` check actually depends on real CI rather
  than passing trivially.

The \`required\` change keeps the single-aggregate-gate contract — new
blocking checks should be added to \`needs:\` here rather than as
separate workflows that branch protection has to track individually.
WomB0ComB0 added a commit that referenced this pull request May 4, 2026
* ci: add governance workflows and harden required gate

Adds the docs-specific CI governance workflows on top of the placeholder
required gate (#5).

New workflows
- workflows/lychee.yml      — link checker (markdown + mdx + docs.json)
- workflows/i18n-parity.yml — informational locale parity report
- workflows/labeler.yml     — auto-label PRs by touched paths
- workflows/stale.yml       — close abandoned issues/PRs
- labeler.yml               — labeler action config

Hardened
- workflows/required.yml — adds mintlify broken-link job to needs:, so
  the aggregate \`required\` check actually depends on real CI rather
  than passing trivially.

The \`required\` change keeps the single-aggregate-gate contract — new
blocking checks should be added to \`needs:\` here rather than as
separate workflows that branch protection has to track individually.

* ci: make mintlify/spectral advisory, scope labeler area:content

Resolves CI failures and review feedback on this PR.

required.yml
- mintlify (broken-links): set continue-on-error until #6 (rewrites
  api-reference/introduction.mdx) and #7 (deletes essentials/ starter
  pages) merge. Five broken links here all live in those soon-to-be-
  removed files.
- spectral (OpenAPI lint): fix invalid action SHA — use v0.8.13 tag
  with TODO for Dependabot to SHA-pin. Mark advisory.
- pwa-manifest: skip gracefully when manifest.webmanifest is absent
  (it lives on feat/brand-assets PR #8). Once #8 merges, this gate
  becomes substantive on main.
- required: gate now blocks only on pwa-manifest. Mintlify and spectral
  results print for visibility.

labeler.yml
- area:content: add all-globs-to-all-files exclusion for paths owned by
  other labels (api-reference, specs, locales, .github, repo guidance)
  so PRs don't accumulate redundant labels.

* ci: flip mintlify back to blocking now that #6 and #7 merged

The advisory mode was scoped to "until docs/onboarding-pages and
chore/repo-cleanup land". Both are now in main:
- #6 (81ab409) rewrote api-reference/introduction.mdx (no more
  /api-reference/endpoint/* dangling refs)
- #7 (c6bf336) deleted the essentials/* and ai-tools/* starter pages
  (no more /writing-content/embed and /api-playground/demo broken links)

The five broken links the original run found are gone. mintlify
(broken-links) returns to a substantive blocking gate.

spectral remains advisory until the stoplightio/spectral-action SHA
pin lands (Dependabot will handle).
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.

1 participant