| Summary: | `git webkit pr --no-commit` spits out a bunch of errors when there are multiple commits on a branch | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | ap, bfan2, jbedard, ryanhaddad, simon.fraser, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 16 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=265030 | ||
|
Description
Simon Fraser (smfr)
2023-09-19 17:55:53 PDT
I think there's multiple things here — * We expect the branch to be what's being pushed, and what the PR is being created from, * That check-webkit-style fails with multiple commits on a branch. The latter is what I assumed the bug was about from the title, but it sounds from the body like what you're actually trying to achieve is creating a PR with a single commit? To actually do that implies we'd do something like: 1. Create a new branch (B') based on the merge-base of the current branch (B), 2. Cherry-pick the top of B onto B', 3. Then run the "normal" git-webkit pr flow on B'. Does that seem right? (In reply to Sam Sneddon [:gsnedders] from comment #2) > I think there's multiple things here — > > * We expect the branch to be what's being pushed, and what the PR is being > created from, > > * That check-webkit-style fails with multiple commits on a branch. > > The latter is what I assumed the bug was about from the title, but it sounds > from the body like what you're actually trying to achieve is creating a PR > with a single commit? > > To actually do that implies we'd do something like: > > 1. Create a new branch (B') based on the merge-base of the current branch > (B), > 2. Cherry-pick the top of B onto B', > 3. Then run the "normal" git-webkit pr flow on B'. > > Does that seem right? And if you were doing that, you wouldn't run into the check-webkit-style bug because at that point you'd be running it against a branch with a single commit. |