* 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.
Our previous strategy was to code owner all the specific files we should
own but that's fragile and unreasonable. This is simpler. We expect
there will still be edge cases that live outside these directories (e.g.
*Application*kt).
* For #15278: added CoroutineManager to count runBlocking calls
* For #15278: Added actual detekt rule for runblocking and its config to the yaml
* For #15278: Added unit test for RunblockingCounter
* For #15278: renamed StrictModeStartupSuppressionCountTest.kt to PerformanceStartupTest.kt and added runBlockingCount test
* Lint fix
* For #15278: made runblocking a Long to prevent overflow
* For #15278: fixed MozRunblocking name, description and moved RunBlockingCounter to perf package
* For #15278:Renamed MozillaRunblockingCheck to MozillaRunBlockingCheck
* For #15278: Added setup for unit test, since it failed without restting counter
* For #15278: Fixed naming for RunBlocking lint check
* For #15278: removed changes made to test to use runBlockingIncrement
* For #15728: added test exclusion for runBlocking check
* For #15278: changed null check and added Synchronized to count setter
* For #15278: fix for nits
* For #15278: added StartupExcessiveResourceUseTest to CODEOWNERS
* For #15278: fixed for nits
* For #15278: Moved increment function to extension function and fixed indentation
* For #15278: Added tests for Atomic Integer extension and nit fix
The "Can you reproduce in Firefox for Android?"-question that is now obsolete since Fennec is EOL. Also, fenix uses the shield icon to open ETP toggle, and not the lock icon
Currently, users file performance issues and it's up to the Fenix team
to triage them and tag them appropriately. I think it'd save the Fenix
team time and ensure the performance team sees more issues if there was
a new issue type.
