elm_rebase.sh bookmarks a non-public commit if MOZ_TOP_FF is a non-public commit
Categories
(Core :: WebRTC, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox111 | --- | unaffected |
| firefox112 | --- | wontfix |
| firefox113 | --- | wontfix |
| firefox114 | --- | fixed |
People
(Reporter: mjf, Assigned: mjf)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
Modifications in Bug 1820982 added changed where the bookmark was added to $MOZ_TOP_FF. However, if rebasing non-public commits, adding the bookmark at $MOZ_TOP_FF will inadvertently push non-public commits to the repo when the bookmark is pushed, which not intended behavior. We should bookmark the top public commit (the previous public head of elm) even when rebasing non-public commits.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1820982
| Assignee | ||
Comment 2•2 years ago
|
||
We don't want to accidentally push non-public commits when pushing
the new bookmark during a rebase.
Depends on D174385
Updated•2 years ago
|
| Assignee | ||
Comment 3•2 years ago
|
||
Depends on D174386
Updated•2 years ago
|
Comment 5•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/d36656437fc8
https://hg.mozilla.org/mozilla-central/rev/c35b4a881395
Comment 6•2 years ago
|
||
The patch landed in nightly and beta is affected.
:mjf, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox113towontfix.
For more information, please visit auto_nag documentation.
Description
•