The update-nimbus-experiments workflow creates PRs that don't schedule a
`complete-pr` task (because the github-actions bot is untrusted), but in this
case we have a `complete-push` task which is good enough.
Bump top site limit under its new name
Fix unresilved conflict
Allow Nimbus to generate code that allows the fork flavors
Drop private browsing page again
Use the new text color name
Point at paged style again
Bring back Sentry so we don't have to change the code that would call it
Note we need to build with app: now for some reason
Also prefix Github build commands
Adapt to settings moving
Parse Iceraven versions
Discover the linter's formatter
Get rid of some Detekt complaints
Handle more weird version strings
Finish README
Stop auto-release changelogs from being too huge
Fix#440 by reattaching settings
PRs created by github actions don't get a pull-request taskcluster graph
scheduled (because that is only done for PRs created by collaborators).
However, if the PR is created in the main fenix repo, typically because
it comes from one of our internal github workflows, then we get a push
graph, which is sufficient to run the required checks.
This change lets mergify consider a green `complete-push` task as
sufficient to queue a PR (in addition to all the other conditions, e.g.
wrt review), which will allow PRs created by the
update-nimbus-experiments workflow to be queued by mergify instead of
having to be merged by a repo admin.
* Let relbot update A-C on trunk
We already use relbot for this on fenix release branches and on all
branches for focus-android, so might as well avoid the duplication.
* Update mergify rules to auto-merge AC bumps from relbot on the main branch
PR tasks/checks do not run for relbot and therefore the existing mergify doesn't work. Instead we can look at the "push tasks". But since there is no "push complete" task yet, I listed all checks manually.
akliuxingyuan
Julien Cristau
Adam Novak
Johan Lorenzo
Sebastian Kaspari
Ben Hearsum
Stefan Arentz
Sebastian Kaspari