Bug 240445
| Summary: | [GitHub] Why merged PRs have no commits/files changed information? | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Manuel Rego Casasnovas <rego> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | ap, fujii.hironori, jbedard, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 239082 | ||
Manuel Rego Casasnovas
When a PR gets merged it looks like it lost all the information regarding the commit and the changes made by that PR.
I believe it'd be useful to still see the changes there, like in a regular GitHub project.
Also I believe we are going to be losing context and information compared to the bugzilla workflow. In a complex patch that might have several review iterations and that might change the design or whatever, you'll have no way to see previous versions of the patch, or understand the review comments as you won't have the whole context anymore.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
This is not intentional, and will stop happening once GitHub becomes the source of truth. I couldn't find an existing bug for this though.
Manuel Rego Casasnovas
(In reply to Alexey Proskuryakov from comment #1)
> This is not intentional, and will stop happening once GitHub becomes the
> source of truth. I couldn't find an existing bug for this though.
Good to know, I guess there's nothing to do until the GitHub transition is complete.
Feel free to close this or keep it open for tracking purpose, as you prefer.
Radar WebKit Bug Importer
<rdar://problem/93522063>