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
to validate and publish metrics, per https://mozilla.github.io/glean/book/user/adding-glean-to-your-project/enable-data-ingestion.html#validate-and-publish-metrics
> After your product has been enabled, you must submit commits to probe scraper to validate and publish metrics. Metrics will only be published from branches defined in probe scraper's repositories.yaml, or the Git default branch if not explicitly configured. This should happen on every CI run to the specified branches. Nightly jobs will then automatically add published metrics to the Glean Dictionary and other data platform tools.
These directories are specific to Fenix. After a quick scan and chat
with Releng, we don't have knowledge / motivation to be maintainers
here.
Releng will continue to be CODEOWNERS of core taskcluster files though.
* Update Fenix release checklist
Updating this to reflect the latest process for releases for Firefox for Android.
* Incorporating feedback.
Incorporating review feedback.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* Disable run-ui in build-contributor-pr workflow
Unfortunately the problem with INSTALL_FAILED_INSUFFICIENT_STORAGE is still showcasing itself on v2.21.0 – I'm not aware of any workaround at this moment in time, so I'm disabling this step of the workflow again.
* Update build-contributor-pr.yml
* Fixes#11427 - Rename master branch to main (Automation/TC)
* Fixes#11427 - Rename master branch to main (GitHub Workflows)
* Fixes#11427 - Rename master branch to main (GitHub Workflows)
* Fixes#11427 - Rename master branch to main (GitHub Issue Templates)
* Fixes#11427 - Rename master branch to main (Jenkins)
* Fixes#11427 - Rename master branch to main (README & Documentation)
* Fixes#11427 - Rename master branch to main (Jenkins)
* Fixes#11427 - Rename master branch to main (Random)
Github supports a more useful templating system that can provide
hints, descriptions, and simple data validation.
We can try to use this to increase the quality of our bug reports.