How to Contribute to android/nav3-recipes
A practical guide backed by android/nav3-recipes's real pull-request history - not guesswork.
79%
PR merge rate
no recent data
First review
100%
First-timer success
A Tier
C-Rank
Your game plan
1
Pick a starter issue
android/nav3-recipes currently labels 5 open issues as "good first issue". Start there - maintainers expect newcomers on those.
2
Time your pull request
Median first review lands within no recent data. Open your PR when maintainers are active rather than right before a weekend.
3
Keep it small and focused
Outside PRs to this repo are merged at a 79% rate. Small, well-described PRs that pass CI consistently outperform large ones.
4
Engage with review feedback
10 active maintainers review contributions here. Respond to comments promptly - responsiveness is the strongest predictor of getting merged.
Open good first issues
[Recipe request] A base class that implements the common patterns for decorating scenes
#324[Recipe request] rememberNavKey helper
#323Add recipe for composite DeepLinkMatcher.Filter
#322[Recipe request] Add deep link recipe with DeepLinkKey interface
#304[Recipe Request] Add deep link recipe for creating synthetic back stack
#302Looking for more? See best Kotlin repos for beginners.