[ci] allow claude to open PRs for certain instructions.#13536
[ci] allow claude to open PRs for certain instructions.#13536
Conversation
github-actions
Bot
added
size/M
github-actions
Bot
added
size/M
github-actions
Bot
added
size/M
yiyixuxu
left a comment
yiyixuxu
left a comment
There was a problem hiding this comment.
thanks!
i left a comment,
| CLAUDE_COMMIT=$(git rev-parse HEAD) | ||
|
|
||
| git fetch --depth=1 origin "$BASE_BRANCH" | ||
| git switch -c "$NEW_BRANCH" "origin/$BASE_BRANCH" |
There was a problem hiding this comment.
ohhh i think, if we alreeady at a claude PR -> it's better if we stay there until we merge no?
so basically if i said COMMIT this from a contributor's PR -> claude open a new PR -> we iterate there where claude can directly commit into its own PR -> merge
github-actions
Bot
added
size/M
github-actions
Bot
added
size/M
|
@yiyixuxu a gentle ping. |
yiyixuxu
left a comment
yiyixuxu
left a comment
There was a problem hiding this comment.
thanks
let's merge it as it is and then let's open a dummy PR to test fully how it works in action, and iterate as needed?
| COMMIT THIS (uppercase). If committing, only touch src/diffusers/ and .ai/. | ||
| COMMIT THIS (uppercase). If editing, only touch files under src/diffusers/ or .ai/. | ||
| A separate workflow step will commit your edits and open a follow-up PR — do NOT | ||
| run git yourself, and do NOT report on commit/push/PR status in your reply. |
There was a problem hiding this comment.
just curious what is this for
There was a problem hiding this comment.
Without this line, Claude tends to wrap up its reply with a made-up comment (it can't know the branch name or PR URL), and we'd end up with two conflicting status comments on the PR.
2 participants
What does this PR do?
Potentially fixes #13472 (comment)