アセット更新ラッパーを追加（共有ワークフロー方式・#141 を置き換え） - #142
Merged
Merged
Conversation
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.
概要
WordPress.org のアセット（アイコン・バナー・スクリーンショット）をリリースと独立して反映するための薄いラッパーを追加する。共有 reusable workflow (
tarosky/workflows/.github/workflows/asset-update.yml) をworkflow_dispatchで呼び出すだけ。背景・方針
当初は各リポジトリに個別の
asset-update.ymlを追加する案（本リポジトリでは #141）だったが、以下の理由で共有ワークフロー方式に一本化した（tarosky/workflows#121, tarosky/workflows#122）。10up/action-wordpress-plugin-asset-updateは readme.txt を trunk へ無条件同期するため、main に未リリースの README があると公開ページに漏洩するリスクがある共有ワークフローは 自前の assets-only SVN commit を採用しており、trunk / readme.txt には一切触れない。そのため
workflow_dispatchをいつ実行しても未リリース README が漏れることはない。この方針転換に伴い、旧 #141 はクローズする。
Refs tarosky/workflows#121