Bug 240085
| Summary: | [git-webkit] Verify forks after creation | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jonathan Bedard <jbedard> |
| Component: | Tools / Tests | Assignee: | Jonathan Bedard <jbedard> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Jonathan Bedard
Forking a repo in GitHub is not instant, and `git-webkit setup` may fail if creation of a private fork takes longer than we expect it to.
First, we should have a better error message in this case. We should also be a bit more patient, GitHub advertises that forking may take a minute or two.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/92978491>
Jonathan Bedard
Pull request: https://github.com/WebKit/WebKit/pull/568
Jonathan Bedard
Changing the title of this bug slightly because there is a very similar problem involving private forks coming from repos with the same name.
Jonathan Bedard
Landed https://commits.webkit.org/250423@main