-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CONTRIBUTING.md for better guidance for new contributors #1259
base: main
Are you sure you want to change the base?
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1259 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 373 373
Branches 94 94
=========================================
Hits 373 373 ☔ View full report in Codecov by Sentry. |
I also noticed that the triage process doesn't say anything about discussing solutions to identify the actions that need to take place. The status goes from "triage" to "available". I think there should be an "in discussion" step that indicates, "Yes this is a valid issue, but we're uncertain how we want to address it. Opinions are welcome." |
I think these changes are helpful. |
Can we please merge this? @gregsdennis @Relequestual |
The suggestions we made haven't been implemented. |
Summary
We are making it more clear for new contributors the conditions to work on an Issue and submit a PR.