Repository navigation
Contributing: Aligned templates, labels and workflows with the other repositories - #117
Merged
Merged
Conversation
…epositories The repository used the upstream fork's setup while chronica, fabrica and Identica share one through whereareiam/devops: - Pull request checks move to pull-request-checks.yml and a reusable verify workflow, run for every pull request (stacked ones included) and skip drafts. - The title and label check uses devops' validate-metadata, which also checks the "Area: Description" title. - The release drafter uses the shared categories and regroups the draft by area, taking the summary and compatibility section from .github/release-notes.md. - A pull request template, Dependabot for npm and GitHub Actions, and bug report and suggestion templates whose labels exist; the upstream templates applied labels the repository does not have. - CONTRIBUTING documents the past-tense titles, the areas and labels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brings the repository's GitHub setup in line with chronica, fabrica and Identica, which share theirs through
whereareiam/devops.pull-request-checks.ymlcalls a newreusable-verify.ymlwith the same Prettier, TypeScript, Vitest and build jobs. They now run for every pull request, so a stacked pull request is checked too; until now they ran only for pull requests intodev. Drafts are skipped, and editing a title no longer reruns the build.pull-request-metadata.ymluseswhereareiam/devops/primitive/pull-request/validate-metadata@v3, which checks theArea: Descriptiontitle as well as the one release label. It replaces themheap/github-action-required-labelsjob.whereareiam/devops/primitive/release/draft/regroup@v3. The summary and the Forgejo compatibility section now come from.github/release-notes.md(set to 0.5.0), so the draft no longer needs hand edits.style bug,core bug,documentationandenhancement, none of which exist here, so no issue was ever labelled.bun.lockis not committed, so it works frompackage.json) and GitHub Actions, labelleddependencies.Area: Descriptiontitles, the list of areas, the label table and the release notes file.The labels on GitHub already match the other repositories' colours and descriptions, and
suggestionwas added.Kept as they were:
release-build.ymlwith thebuild-release-assetsaction, and the manualdevelopment-build.yml. ESLint stays off until typescript-eslint supports TypeScript 7.Checks
🤖 Generated with Claude Code