Conversation
…update Bumps the npm_and_yarn group with 1 update in the / directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Bumps the npm_and_yarn group with 1 update in the /apps/web directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Updates `vite` from 7.3.1 to 7.3.2 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v7.3.2/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.3.2/packages/vite) Updates `vite` from 7.3.1 to 7.3.2 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v7.3.2/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.3.2/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.3.2 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: vite dependency-version: 7.3.2 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
…nd_yarn-20b630b4a0 chore(deps): bump the npm_and_yarn group across 2 directories with 1 update
ci: automate staging-first branch flow
sync: merge main back into staging
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
Walkthrough
変更内容
Sequence Diagram(s)sequenceDiagram
participant Git as "Git (push)"
participant GHWF as "GitHub Actions\n(sync-main-to-staging)"
participant Script as "sync-main-to-staging.sh"
participant GHAPI as "GitHub API\n(compare / pr / labels)"
Git->>GHWF: push to main (or manual)
GHWF->>Script: run script with env (GH_REPO, SYNC_SHA, ...)
Script->>GHAPI: GET open PRs (search base=head)
alt existing PR found
GHAPI-->>Script: return PR URL
Script-->>GHWF: log and exit
else no existing PR
Script->>GHAPI: GET compare base...head
alt ahead_by == 0
GHAPI-->>Script: ahead_by = 0
Script-->>GHWF: log "nothing to sync" and exit
else ahead_by > 0
Script->>GHAPI: POST create PR (title, body)
GHAPI-->>Script: return PR URL/number
Script->>GHAPI: PATCH add labels / assignees / reviewers
Script-->>GHWF: log PR created
end
end
推定コードレビュー工数🎯 4 (Complex) | ⏱️ ~45 minutes 関連する可能性のあるPR
詩
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
dosubot
Bot
added
dependencies
Merging this PR will not alter performance
Comparing 
Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request automates the synchronization between the main and staging branches by introducing a new script, sync-main-to-staging.sh, which automatically creates or reuses a sync PR after pushes to main. Additionally, the enforce-staging-flow.sh script has been simplified by removing the admin bypass logic and author-related metadata. Documentation in README.md and .github/copilot-instructions.md has been updated to align with these workflow changes. I have no feedback to provide.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
ci: pin checkout in sync workflow
coderabbitai
Bot
added
the
documentation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/scripts/sync-main-to-staging.sh:
- Around line 64-69: Update the gh pr create invocation to include desired
reviewers/assignees and labels so automated sync PRs are easier to triage: add
the --assignee (or --reviewer) flag with a default user or team and add one or
more --label flags (e.g., "sync","automated"), referencing the existing
variables used in the command (GH_REPO, BASE_BRANCH, HEAD_BRANCH, title, body)
and ensure any labels you add are created beforehand or create them in the
script prior to calling gh pr create.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: a0cf83e0-93c9-44d5-99f7-231bdf70e1b1
📒 Files selected for processing (5)
.github/copilot-instructions.md.github/scripts/enforce-staging-flow.sh.github/scripts/sync-main-to-staging.sh.github/workflows/sync-main-to-staging.ymlREADME.md
Configure sync-main-to-staging automation to create or update labels before PR creation, and pass label/assignee/reviewer metadata to gh pr create via env-configurable values. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ci(sync): add metadata for automated main->staging PRs
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/sync-main-to-staging.yml:
- Around line 17-33: The workflow hardcodes the default assignee/reviewer value
"is0692vs" for the SYNC_PR_ASSIGNEES and SYNC_PR_REVIEWERS env vars in the
open-sync-pr job; change the defaults to rely on repository variables instead of
a specific username by removing or replacing the hardcoded 'is0692vs' fallback
so that SYNC_PR_ASSIGNEES and SYNC_PR_REVIEWERS use vars.SYNC_PR_ASSIGNEES and
vars.SYNC_PR_REVIEWERS (or an empty string) as the default in the job
environment, ensuring the script receives configurable values rather than a
single hardcoded user.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 1f136a25-3d05-4971-bf9d-8a4a849c70bd
📒 Files selected for processing (2)
.github/scripts/sync-main-to-staging.sh.github/workflows/sync-main-to-staging.yml
Use repository variables (or empty values) for SYNC_PR_ASSIGNEES and SYNC_PR_REVIEWERS so sync automation stays configurable and avoids a fixed username. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ci(sync): remove hardcoded assignee/reviewer fallback
Merged
This was referenced Apr 13, 2026
Closed
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.
Summary:
Included changes:
Notes:
Greptile Summary
このPRは、CI/CDのブランチ管理フローを2つの面から強化します。①
enforce-staging-flow.shから admin bypass ロジックを削除し、全ユーザーに staging-first ルールを均一適用するように変更。②新たにsync-main-to-staging.ymlワークフローとsync-main-to-staging.shスクリプトを追加し、mainへのプッシュ後に自動でmain → stagingの同期 PRを開くようにしました。author_has_admin_bypass()関数と関連コードを削除。管理者権限を持つユーザーでもmain直接ターゲットの PR はstagingにリターゲットされるようになります（意図的な変更）。mainへのプッシュ時にsync-main-to-staging.shが既存のオープン sync PR を確認し、なければahead_byが 0 かどうかチェックし、新規 sync PR を作成します。重複 PR 防止ロジックも組み込まれています。copilot-instructions.mdとREADME.mdを新しいフローに合わせて更新。sync-main-to-staging.ymlのactions/checkout@v4がコミット SHA にピン留めされていないため、アクション更新で予期せぬ挙動変化が生じる可能性があります（ベストプラクティス）。Confidence Score: 5/5
このPRはマージして安全です。CI/CD自動化スクリプトの追加・整理であり、アプリコードへの影響はありません。
残る指摘はすべてP2（スタイル・ベストプラクティス）であり、ロジック上のバグや運用上の致命的問題は見当たりません。admin bypass の削除は意図的かつ文書化されており、sync スクリプトの重複 PR チェック・dry-run 対応も適切です。
.github/scripts/sync-main-to-staging.shと.github/workflows/sync-main-to-staging.ymlは新規追加ファイルのため、本番環境での初回動作を注視してください。Important Files Changed
Sequence Diagram
sequenceDiagram participant Dev as 開発者 participant GH as GitHub participant EW as enforce-staging-flow.yml participant SW as sync-main-to-staging.yml participant Script as sync-main-to-staging.sh Dev->>GH: feature → main の PR を作成 GH->>EW: pull_request_target トリガー EW->>GH: PR のベースを staging に変更 (retarget) GH-->>Dev: コメント通知 Dev->>GH: feature → staging の PR を作成・マージ Dev->>GH: staging → main の PR を作成・マージ GH->>SW: push to main トリガー SW->>Script: bash sync-main-to-staging.sh Script->>GH: open sync PR を検索 alt sync PR が既存 Script-->>SW: PR URL を出力して終了 else sync PR なし Script->>GH: main vs staging の ahead_by を確認 alt ahead_by > 0 Script->>GH: main → staging の sync PR を作成 GH-->>Dev: sync PR 通知 else ahead_by = 0 Script-->>SW: 同期不要として終了 end endPrompt To Fix All With AI
Reviews (1): Last reviewed commit: "Merge pull request #344 from Hiroki-org/..." | Re-trigger Greptile
Context used: