Labels
Labels
35 labels
- Creating or updating github actions
- Requires substantive thought about the API or architecture of the codebase
- Apply if the issue is in the annual plan (eg belongs to technical strategy)
- Apply if the issue is not in the annual plan (eg spontaneous request from W&S team)
- Related to the back end
- Work has started but is held up by another issue
- Unintended behaviour in any area of the app
- Related to website or marketing content
- A decision is required (eg on UX or company policy)
- Significant updates to dependencies are required
- Related to visual design
- Improves our lives/efficiency as developers
- System admin and devops
- Improvements or additions to documentation
- This issue or pull request already exists
- A new feature of the app
- Run the chromatic check only if the PR has this label
- Related to the front end
- Related to GIS strategy or process
- A good first issue for new or junior developers
- Applied by the assigned developer if they need help
- Apply if assignee expects significant learning curve, complexity or unknowns
- Apply if assignee expects some complexity or may need to check a few things
- Apply if assignee is clear on how to do the issue and expects no problems
- If you want to run cool, you've got to run on heavy, heavy fuel
- Apply to an epic when it is fully qualified (checklist is complete)
- Further information is requested
- A quick win for us to push through if we have a few minutes before getting back to the big stuff
- Quirky UX or styling problems that aren't major but reflect poorly on us
- Actual engineering computation or analytics