637
edits
BMO/Recent Changes: Difference between revisions
Jump to navigation
Jump to search
→Recent Changes
DaveLawrence (talk | contribs) |
DaveLawrence (talk | contribs) |
||
| Line 1: | Line 1: | ||
= Recent Changes = | = Recent Changes = | ||
== 2023-03-13 == | |||
[https://github.com/mozilla-bteam/bmo/tree/release-20230313.1 release-20230313.1] | |||
* {{bug|1820859}} Wrap code that looks for a latest nightly/stable versions of Firefox in try/catch block in case of failure | |||
* {{bug|1821251}} Quick search box can't be activated in screen reader browse mode | |||
* {{bug|1821521}} [GITHUB] Only perform actions to a bug if branch is main, master, or a release branch. Ignore feature, bugfix branches, etc. | |||
* {{bug|1821679}} [GITHUB] Display the name of the branch the commit was made in the comment added to the bug | |||
* {{bug|1821694}} [GITHUB] Commits made to release branches should not close the bugs, only add status flag and comment | |||
* {{bug|1821739}} [GITHUB] When a status flag is set from a commit, the flag is stored in the flags table, but it is not recorded properly in the bugs_activity table | |||
* {{bug|1821478}} [GITHUB] Fall back to author.name if author.username is missing | |||
* {{bug|1821386}} Set the Milestone field when resolving bugs after PR merges | |||
== 2023-03-08 == | == 2023-03-08 == | ||
| Line 32: | Line 44: | ||
* {{bug|1812457}} we are unconditionally setting release-managers review on the patch when we detect the change, even when release-managers has already given an r+ review. | * {{bug|1812457}} we are unconditionally setting release-managers review on the patch when we detect the change, even when release-managers has already given an r+ review. | ||
* {{bug|1812606}} github pull request with the same number but from different repos get confused | * {{bug|1812606}} github pull request with the same number but from different repos get confused | ||
= Archive = | = Archive = | ||