Confirm
328
edits
Changes
→Commit: sheriffs watch our backs
You can't commit to mozilla-central / mozilla-inbound until you have "level 3" access, so you'll need someone to do this for you. Try asking in [irc://irc.mozilla.org/#jsapi #jsapi], or add the <code>checkin-needed</code> keyword to the bug. After you have been contributing for a while, you can get level 3 access by [https://www.mozilla.org/hacking/commit-access-policy/ applying for it].
After committing, a large series of tests will be run to make sure you didn't break anything. You'll will need to hang around to make sure you didn't break something. Check [http://tbpl.mozilla.org/?tree=Firefox It is difficult to determine what failures are real and what are what we call "intermittent oranges" ("orange" because that is the Firefox tree] color used on our continuous integration dashboard for test failures). Sometimes failures If you do break something, a sheriff will probably let you know via IRC and will be spurious: probably back your patch out. You can always ask [irc://irc.mozilla.org/#jsapi for help] determining when this what is the case, to startgoing on. (Over time you'll figure get a feel for figuring out when this breakage is and isn't the case yourselfreal on your own.)
== Overview of the JS engine ==
