You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: add release preparation and publication workflows - #20
Add the release automation used by the other Hoverkraft action repositories, pinned to ci-github-publish 3.0.0.
__prepare-release.yml applies Conventional Commit release labels on PR events and prepares configuration on main pushes.
__release.yml supports manual dispatch and Monday releases at 08:25 UTC. It runs the full shared CI on the default branch, then plans and publishes that exact commit. No-change plans skip publication; manual force only bypasses that guard. The CI bot token lets the published tag trigger subsequent workflows.
__main-ci.yml handles tag pushes and invokes shared action-documentation generation after successful CI. Tag pushes and manual main runs refresh all action references; internal workflows remain excluded, and documentation PRs use squash merging.
CONTRIBUTING.md documents the commands, schedule, credentials and behavior.
The existing organization variable CI_BOT_APP_CLIENT_ID and secrets CI_BOT_APP_PRIVATE_KEY and OPENAI_API_KEY are available to this repository. Publication requests contents-write and pull-request-read permissions; documentation automation requests contents, pull-request and workflow write permissions.
Validation: make test passes all 43 tests, and make lint passes, including actionlint, formatting and security checks. The preparation workflow is exercised by this PR; publication and tag-triggered documentation writes require the workflows to be merged and have not been executed during validation.
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
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.
Add the release automation used by the other Hoverkraft action repositories, pinned to ci-github-publish 3.0.0.
__prepare-release.ymlapplies Conventional Commit release labels on PR events and prepares configuration on main pushes.__release.ymlsupports manual dispatch and Monday releases at 08:25 UTC. It runs the full shared CI on the default branch, then plans and publishes that exact commit. No-change plans skip publication; manualforceonly bypasses that guard. The CI bot token lets the published tag trigger subsequent workflows.__main-ci.ymlhandles tag pushes and invokes shared action-documentation generation after successful CI. Tag pushes and manual main runs refresh all action references; internal workflows remain excluded, and documentation PRs use squash merging.CONTRIBUTING.mddocuments the commands, schedule, credentials and behavior.The existing organization variable
CI_BOT_APP_CLIENT_IDand secretsCI_BOT_APP_PRIVATE_KEYandOPENAI_API_KEYare available to this repository. Publication requests contents-write and pull-request-read permissions; documentation automation requests contents, pull-request and workflow write permissions.Validation:
make testpasses all 43 tests, andmake lintpasses, including actionlint, formatting and security checks. The preparation workflow is exercised by this PR; publication and tag-triggered documentation writes require the workflows to be merged and have not been executed during validation.