Submitting for review
After checking in all of your wonderful changes to your
strong-component git branch. Push it up to Github.Be descriptive of your changes! The more the better. If possible, include screenshots or GIF demos. Add the appropriate label(s) that describe your changes.
Since we're adding a brand new component, we'll add the
feature label.Assign or
@ at least one code reviewer and one design reviewer. This is required if you're creating a brand new component. If you're unsure who to tag, default to @itsjonq and @digitaldesigner.A Netlify deploy preview for your Pull Request will automatically be generated. To make it easier for reviewers to QA your updates, provide them with a direct link to your Story either in the Pull Request description or as an additional Github comment.
Every pull request automatically fires off a Travis build. Once that passes, it'll generate a code coverage score.
The Travis build must be green and the coverage score must be 100% before merging into
master.Last modified 3yr ago