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.
Issues
Good First IssueA well documented issue explaining the tasks needed to accomplish it, that should be suitable for a new contributor to the project
💥 BugThe problem reported has been tested and the effect replicated by a maintainer
🔦 Help WantedMy code is broken and I don't know why. I need help!
❔ QuestionSeeking information that doesn't include code. e.g “can I use react navigation with react-native-elements?”
⏳ Awaiting ReplyMaintainer 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 ReleaseIssue or feature has been implemented and will be apart of the next npm release
📥 PR SubmittedA pull request has been submitted to resolve this issue or implement this feature
Pull Requests
💊 Bug FixFixes a bug reported in an issue
📞 Needs Response from AuthorMaintainer has left feedback on the pull request and it needs a response or a revision made from the author
📦 RELEASEPull request for the next version to be released
👨💻 WIPWork In Progress. Author is still working on this PR and it shouldn't be merged or reviewed as yet
Both
🤔 Thoughts?Requires discussion for decisions that are unsure
🔧 ToolingIssues or pull requests that affect tooling e.g tests, npm, ci
📖 DocsIssues or pull requests surrounding documentation
✨ EnhancementSuggests and implements improvements or additions to existing components
💡 New ComponentSuggests or implements a new component
🗂 TypesIssues and pull requests around typescript definitions