CI Automation: Difference between revisions

Find a string in Firefox (e.g in one of the menus or preference dialogs) and make sure that it's fairly unique. Then try and use [https://searchfox.org/mozilla-central/source searchfox] to find where that string is defined. Change the value to something else and re-run a build. Then use '''./mach run''' to see if your change is there!

==== Fixing the Bug ====

Once you have your fix commit it with a message that follows [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Committing_Rules_and_Responsibilities#Checkin_comment Mozilla's guidelines]. Be sure to test your patch (ask your mentor if instructions for testing weren't included in the bug). You should also run '''./mach lint --outgoing''' to make sure you didn't cause any lint errors. If the patch is complicated enough, your mentor might also want to do a [https://firefox-source-docs.mozilla.org/tools/try/index.html try push] (you won't have permission to do this on your own, so they'll do it on your behalf).

==== The Review Cycle ====

Once you have the requested changes amended to the proper commits, you can re-submit them to phabricator and the process will repeat itself.

==== What to Expect After Landing ====

If all the builds and tests pass on the integration branch, your patch will eventually be merged into mozilla-central (these merges typically happen twice a day). At this point you're in the clear! The next time someone pulls in the latest changes from central, your changes will be included. Congratulations!

== [[Glossary]] ==

Mozillians use a dizzying amount of terminology that can make any new contributor's head spin. You'll often be able to find what you're looking for in the [[Glossary]]. If you come across something not mentioned there, feel free to ask us in IRC (and remind us to add it to the list).