fix: correct release trigger description from push tags to GitHub Release#27
Merged
Conversation
…ease - All 5 RELEASE.md: change trigger condition from 'push tag' to 'create GitHub Release' - .github/workflows/publish.yml: add missing pi-vision-tools case branch
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
1 participant
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.
变更内容
所有 5 个
RELEASE.md：触发条件从"推送 git tag"修正为"创建 GitHub Release"，与实际 workflow 配置（release: [published]）保持一致推送 tag（Release 依赖这个 tag 存在），step 4 注释改为创建 GitHub Release（触发发布 workflow），明确 tag 是前置条件、Release 才是触发器.github/workflows/publish.yml：补上缺失的pi-vision-tools-v*)case 分支，确保 pi-vision-tools Release 也能被正确发布