cherry-pickリリース後の同期PRの版数コンフリクト解決手順をスキルに追記#6405
Merged
Merged
Conversation
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough同期ブランチで版数ファイルが衝突した場合の解決手順を追加し、同期PRのマージ前に競合状態とブランチの包含関係を確認するようリリース手順を更新します。 Changesリリース同期と衝突解決
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Member
Author
|
@coderabbitai review |
Contributor
✅ Action performedReview finished.
|
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.
概要
リリースブランチを
masterから切って特定 PR だけ cherry-pick したリリース(create-release-prの「この変更だけ」指定など)の後、dev<-master同期 PR が版数ファイルで衝突する事象と、その解決方針・具体手順を AI 向けドキュメントとしてスキルに追記します。v10.9.1 リリース(#6402 → 同期 #6404)で実際に遭遇したケースの知見です。コード変更は含みません。変更の種類
変更内容
sync-dev-from-masterスキルに「版数ファイルのコンフリクト解決(cherry-pick / hotfix リリース後)」節を追加android/app/build.gradle/app.config.ts/ios/TrainLCD.xcodeproj/project.pbxproj)のみである点master)、ビルド番号はmax(dev, master)(単調増加維持・canary 既発行分との衝突回避)origin/devをマージ →--oursで確定 → ビルド番号だけ引き上げ → semver 差分のみを確認してコミットする具体手順finalize-releaseスキルの手順6に、マージ前のコンフリクト確認ノート(CONFLICTINGなら Ruleset 緩和より先に版数解決)を追加テスト
npm run lintが通ることnpm testが通ることnpm run typecheckが通ること省略: ドキュメント(
.claude/skills/**/SKILL.md)のみでコード変更が無いため、lint / test / typecheck は非該当。関連Issue
スクリーンショット(任意)
Summary by CodeRabbit