This repository was archived by the owner on Jun 21, 2026. It is now read-only.
Repository navigation
[bulk] Sync release automation configuration (2026-02-18-001) - #4
Merged
Merged
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
hdamker
approved these changes
Feb 18, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Release Automation Configuration Sync
Syncs the release automation configuration for TestRepo.
Changes
.github/workflows/release-automation.yml@release-automation)CHANGELOG.mdCHANGELOG/README.mdAbout the release process automation
The release process automation provides slash commands on Release Issues:
/create-snapshot— create a release snapshot with mechanical transformations/discard-snapshot— discard a snapshot and return to planned state/delete-draft— delete a draft release/publish-release --confirm <tag>— publish the releaseRelease Issues are created automatically when
release-plan.yamlis updated on main.Updates to
release-plan.yamlare done via PRs that change only this file.Documentation