devtools/docs/contributor/contributing.md described getting code into the repository as three links: find-bugs.md, fixing-bugs.md and making-prs.md, under a ./contributing/ directory that does not exist. They built to href="#./contributing/find-bugs.md", so the whole "Help with code" path silently went nowhere. Sphinx does not warn about it because a "#" fragment looks like a local anchor. Point the three steps at the general documentation instead, which is what contributor/index.md already tells readers to do: it says this section "only contains technical information specific to Firefox DevTools". Note that DevTools patches go to #devtools-reviewers. bugs-issues.md still split bugs across mozilla-central and the devtools-html GitHub organisation. All DevTools code lives in mozilla-central now, so drop the dead organisation search links and point at filing-good-bugs for how to write an actionable report. For bugs to work on, point at the DevTools project on Codetribute rather than firefox-dev.tools, which no longer lists bugs itself. Differential Revision: https://phabricator.services.mozilla.com/D318454
330 B
330 B
Bugs and issue trackers
DevTools bugs are tracked in Bugzilla, under the DevTools product.
Codetribute lists the mentored and good first bugs available to work on.
For how to write a bug report that someone can act on, see
{doc}/contributing/filing-good-bugs.