Skip to content

Add Gitea Actions parity workflows - #87

Merged
VeryComplexAndLongName merged 2 commits into
mainfrom
feat/gitea-actions-parity
Aug 26, 2026
Merged

Add Gitea Actions parity workflows#87
VeryComplexAndLongName merged 2 commits into
mainfrom
feat/gitea-actions-parity

Conversation

@VeryComplexAndLongName

Copy link
Copy Markdown
Owner

Summary

  • Add .gitea/workflows/quality.yml, mirroring .github/workflows/quality.yml's quality and openspec-validate jobs — the same @openspec-ui/cli validate merge gate on either host.
  • Add .gitea/workflows/require-changeset.yml, gating packages/*/src/** or packages/*/package.json changes on an accompanying .changeset/*.md file.
  • Both were validated end-to-end on a self-hosted Gitea instance (Gitea 1.26.4) as a POC: actions/checkout@v4 ran unmodified, and the require-changeset check correctly failed/passed based on changeset presence.
  • Deliberately not mirrored: extension-integration, release-extension (GitHub-token/gh release-specific), dependency-review (GitHub-only action) — these need host-specific redesign, not a mechanical copy.
  • Does not touch .github/workflows/ — the two directories are additive, ignored by the other host.

Test plan

  • Both new YAML files parse correctly (job names verified via js-yaml)
  • openspec change validate --strict add-gitea-actions-parity
  • npm run lint:english
  • Equivalent workflow logic exercised live on a real Gitea instance during the POC (checkout action + require-changeset pass/fail in both directions)

🤖 Generated with Claude Code

VeryComplexAndLongName and others added 2 commits August 26, 2026 10:39
Mirrors the GitHub quality/openspec-validate merge gate and adds a
require-changeset check, both validated end-to-end on a self-hosted
Gitea instance during a POC. Additive only: .gitea/ and .github/ are
ignored by the other host, so this does not affect the existing
GitHub CI.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
A verbatim Russian quote slipped through because the local lint:english
check was run before the file was staged; check-english.mjs scans only
git-tracked files (git ls-files), so an untracked new file is silently
skipped. CI's lint:english (run against the committed tree) caught it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@VeryComplexAndLongName
VeryComplexAndLongName merged commit ded6f67 into main Aug 26, 2026
6 checks passed
@VeryComplexAndLongName
VeryComplexAndLongName deleted the feat/gitea-actions-parity branch August 26, 2026 07:54
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