Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
This page is meant to help define the workflow process the core team uses. Check out our ZenHub Board to see our current workflow status and what we are currently working on across all 3 repos.
For more information about our labeling system, head on over to our label glossary.
Component Maturity Lifecycle
Components of the draft web design standards have a defined maturity lifecycle that lives outside, but is related to, the workflow of issues and pull requests. You can find the maturity lifecycle here - https://github.com/18F/web-design-standards/wiki/Component-Maturity-Scale. This maturity model is meant to describe how a component goes from inception through becoming an official component of the draft web design standards.
The table below outlines the steps and processes the core team takes when reviewing issues that have been submitted to the repo.
|Done||Code has passed all automated tests, manual checks and content reviews from core team members. It has also been reviewed on staging for browser and device testing. Issue is closed.|
We use the new "review" feature in Github to track the workflow of Pull Requests now. For more information about our process, please read the contributing guidelines.