Repository navigation
ci(ghtools): adopt the shared ghtools pipeline - #10
Merged
Merged
Conversation
Replaces the repository's workflows with the shared ghtools pipeline (will-roscoe/.ghtools, pinned to v1). Settings live in .github/ghtools.toml; the old .github is archived under .github/archive/ and `ghtools deinit` restores it. The README's Validate badge now shows the ghtools workflow. Improved-By: claude-opus-5-5 <anthropic@willroscoe.uk>
will-roscoe
force-pushed
the
ci/ghtools
branch
from
September 27, 2026 23:43
59c2042 to
55ae678
Compare
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.
Moves this repository's CI and releases onto the shared ghtools pipeline (will-roscoe/.ghtools, pinned to
v1).What changes
lint.yaml,test.yaml,validate.yamlandrelease.yamlare replaced by one stub,.github/workflows/ghtools.yml, which calls the shared pipeline. Settings are in.github/ghtools.toml(each line notes where it was detected from).manifest.json's version was bumped by hand. Now each push tomainworks out the next version from Conventional Commit messages (feat→ minor,fix→ patch,type!→ major;+:majoretc. alone on a line forces one), writes it intomanifest.jsonin achore(release)commit, tags it and attaches thecustom_components/intercomzip to the GitHub release.ci:/docs:/chore:commits don't release, so merging this doesn't.ghtools-statusbranch after eachmainrun (nothing is committed tomain)..githubis archived under.github/archive/pre-ghtools-2026-09-28/;ghtools deinitrestores it, andghtools archive pruneremoves the archive once this has proven itself.