Skip to main content
Version: Bleeding Edge ๐Ÿšง

Label Guide

This page explains how we use labels throughout the repo to tag issues and pull requests. Knowing our label structure will help you to be able to triage issues easier and know how to contribute to open issues and pull requests.


Good First Issue

A well documented issue explaining the tasks needed to accomplish it, that should be suitable for a new contributor to the project

๐Ÿ’ฅ Bug

The problem reported has been tested and the effect replicated by a maintainer

๐Ÿ”ฆ Help Wanted

My code is broken and I don't know why. I need help!

โ” Question

Seeking information that doesn't include code. e.g โ€œcan I use react navigation with react-native-elements?โ€

โณ Awaiting Reply

Maintainer has replied to the user and there's been no response. After 2 weeks any issues with this label should be closed as inactive.

โœ… Fixed - Next Release

Issue or feature has been implemented and will be apart of the next npm release

A pull request has been submitted to resolve this issue or implement this feature

Pull Requestsโ€‹

๐Ÿ’Š Bug Fix

Fixes a bug reported in an issue

๐Ÿ“ž Needs Response from Author

Maintainer has left feedback on the pull request and it needs a response or a revision made from the author


Pull request for the next version to be released

๐Ÿ‘จโ€๐Ÿ’ป WIP

Work In Progress. Author is still working on this PR and it shouldn't be merged or reviewed as yet


๐Ÿค” Thoughts?

Requires discussion for decisions that are unsure

๐Ÿ”ง Tooling

Issues or pull requests that affect tooling e.g tests, npm, ci

๐Ÿ“– Docs

Issues or pull requests surrounding documentation

โœจ Enhancement

Suggests and implements improvements or additions to existing components

๐Ÿ’ก New Component

Suggests or implements a new component

๐Ÿ—‚ Types

Issues and pull requests around typescript definitions