Understanding Issue Filters
Nest provides powerful filtering options to help you find issues that match your experience level and interests.Available Filters
Organization
Filter issues by GitHub organization (e.g., “OWASP”)
Repository
Filter issues by specific repository name
State
Filter by issue state:
open or closedLabels
Filter by issue labels like
good first issue, bug, enhancementFinding Issues via the API
You can query issues programmatically using the REST API.List All Issues
organization- Organization name (e.g., “OWASP”)repository- Repository name (e.g., “Nest”)state- Issue state:openorclosedordering- Sort order:created_at,-created_at,updated_at,-updated_atpage- Page number for paginationlimit- Items per page
- cURL
- Python
- JavaScript
Get Specific Issue
Filtering by Experience Level
Good First Issues
Perfect for newcomers to the project:These issues typically:
- Have clear descriptions
- Require minimal context
- Include guidance on implementation
- Are smaller in scope
Intermediate Issues
For contributors with project knowledge:Look for issues labeled:
enhancement- Feature improvementsbug- Bug fixes requiring investigationrefactoring- Code quality improvements
Sorting and Ordering
Choose the right sort order for your workflow:- Newest First
- Oldest First
- Recently Updated
- Least Recently Updated
Finding Issues by Topic
Use the search functionality to find issues by keyword:Frontend Issues
Backend Issues
Documentation Issues
Working with Pagination
The API returns paginated results:Iterate Through All Pages
- Python
- JavaScript
Best Practices for Issue Selection
Start Small
Start Small
Begin with
good first issue labels to understand:- Project structure and conventions
- Development workflow
- Testing requirements
- Code review process
Check for Assignment
Check for Assignment
Before starting work:
- Read the issue completely
- Check if someone is already assigned
- Comment asking to be assigned
- Wait for maintainer confirmation
Assess Time Commitment
Assess Time Commitment
Look for clues about issue complexity:
- Quick wins: Documentation, typos, simple bug fixes
- Medium effort: UI improvements, basic features
- Large effort: Architecture changes, complex features
Understand Context
Understand Context
Before claiming an issue:
- Read all comments and discussion
- Check if there are linked PRs or related issues
- Review any design documents or specifications
- Ask questions if anything is unclear
Example: Finding Your First Contribution
Request Assignment
On GitHub:
- Navigate to the issue URL
- Comment: “I’d like to work on this issue. Could you please assign it to me?”
- Wait for maintainer response
Start Contributing
Once assigned, follow the Contributing Guide to set up your development environment and submit your PR.
Issue State Reference
Issue is currently open and accepting contributions
Issue has been resolved or closed without a fix
Common Issue Labels
| Label | Description | Experience Level |
|---|---|---|
good first issue | Beginner-friendly issue | Beginner |
bug | Something isn’t working | All levels |
enhancement | New feature or request | Intermediate |
documentation | Documentation improvements | Beginner |
help wanted | Extra attention needed | All levels |
priority: high | Urgent issue | Experienced |
wontfix | Will not be worked on | N/A |