DevTools/Creating Good First Bugs: Difference between revisions
< DevTools
Jump to navigation
Jump to search
(Created page with "Getting started working on a first bug is hard. This guide is meant to provide a short list of steps to provide the necessary information to complete a bug. New contributors c...") |
m (Fix casing) |
||
Line 1: | Line 1: | ||
Getting started working on a first bug is hard. This guide is meant to provide a short list of steps to provide the necessary information to complete a bug. New contributors can easily get overwhelmed and frustrated with making an easy fix, as the | Getting started working on a first bug is hard. This guide is meant to provide a short list of steps to provide the necessary information to complete a bug. New contributors can easily get overwhelmed and frustrated with making an easy fix, as the DevTools environment can be complicated. | ||
* Explain the problem in depth and provide the steps to reproduce. | * Explain the problem in depth and provide the steps to reproduce. |
Latest revision as of 16:59, 14 November 2016
Getting started working on a first bug is hard. This guide is meant to provide a short list of steps to provide the necessary information to complete a bug. New contributors can easily get overwhelmed and frustrated with making an easy fix, as the DevTools environment can be complicated.
- Explain the problem in depth and provide the steps to reproduce.
- List files and lines of code that may need to be modified. Ideally provide a patch for getting started.
- Include link to Simple Firefox Build: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build
- Add the keyword
good-first-bug
.
Automatically post a patch to a gist
- Install a gist-cli:
npm install -g gist-cli
- In your bash profile add:
- git:
alias gist-patch="git diff | gist -o -t patch"
- hg:
alias gist-patch="hg diff | gist -o -t patch"
- git:
- Then go to a clean repo, modify the files, and run the command
gist-patch