Confirmed users
796
edits
(Refactorings happened) |
m (→Checklist for shipping a site patch: Update Bugzilla product/component link) |
||
Line 18: | Line 18: | ||
# There should be an issue on GitHub or Bugzilla. In that bug, diagnosis needs to be done first to validate that the issue is indeed caused by a user agent detection (if you plan on adding an UA override), or can be fixed with injecting JS or CSS. | # There should be an issue on GitHub or Bugzilla. In that bug, diagnosis needs to be done first to validate that the issue is indeed caused by a user agent detection (if you plan on adding an UA override), or can be fixed with injecting JS or CSS. | ||
# A [https://bugzilla.mozilla.org/enter_bug.cgi?product=Web%20Compatibility | # A [https://bugzilla.mozilla.org/enter_bug.cgi?product=Web%20Compatibility&component=Interventions Web Compatibility::Interventions] Bugzilla bug must be opened, with the See Also field linking to the original Bugzilla or GitHub issue that contains the diagnosis and justification for a site patch. | ||
# A patch is written and pull request opened against the [https://github.com/mozilla/webcompat-addon GitHub repo], seeking review from a [https://github.com/orgs/mozilla/teams/webcompat/members webcompat team member]. | # A patch is written and pull request opened against the [https://github.com/mozilla/webcompat-addon GitHub repo], seeking review from a [https://github.com/orgs/mozilla/teams/webcompat/members webcompat team member]. | ||
# Once the site patch is validated locally and given an r+, the PR should get merged. | # Once the site patch is validated locally and given an r+, the PR should get merged. |