| Summary: | Allow WPT exporter to know about an existing WPT checkout | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Myles C. Maxfield <mmaxfield> | ||||
| Component: | Tools / Tests | Assignee: | Myles C. Maxfield <mmaxfield> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | ews-watchlist, glenn, jbedard, simon.fraser, webkit-bug-importer, youennf | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Myles C. Maxfield
2021-09-14 18:23:44 PDT
Created attachment 438199 [details]
WIP
The WPT exporter is currently using a separate WPT checkout as it is adding/deleting branches, remotes and so on. It is also checking out branches, resetting hard so it can overwrite changes in the WPT repository. If we make use of an existing WPT checkout through webkit-patch, we should probably make sure this is ok to modify the WPT checkout, or ask user for confirmation. (In reply to youenn fablet from comment #2) > The WPT exporter is currently using a separate WPT checkout as it is > adding/deleting branches, remotes and so on. > It is also checking out branches, resetting hard so it can overwrite changes > in the WPT repository. > If we make use of an existing WPT checkout through webkit-patch, we should > probably make sure this is ok to modify the WPT checkout, or ask user for > confirmation. Good idea. |