ci: label pull requests with database migrations#766
Conversation
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
확인했습니다. 전체 방향은 맞고 CI/merge 상태도 좋습니다.
다만 merge 전에 한 가지는 고치는 게 좋겠습니다. Blocker / 수정 권장
uses: actions/labeler@v6.0.1이 repo의 기존 workflow들은 대부분 third-party Actions를 SHA로 pin하고 있고, 이 workflow는 현재 uses: actions/labeler@634933edcd8ababfe52f92936142cc22ac488b1b그 외 caveat: |
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
dd7f76f to
f1357bf
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. 🚀 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
db migrationpath label for Alembic revision changesactions/labeleron pull requests from forks without checking out PR codeWhy
Merging several green PRs that each add database migrations needs maintainer ordering/oversight even when CI is green.
Test plan
git diff --checkdb migrationrepository labeldb migrationto the currently open migration PRs: feat(accounts): add operator-controlled account aliases #759, feat(accounts): add manual routing policy #761, feat(proxy): route security work to authorized accounts #762