-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
docs: Cleanup CONTRIBUTING.md and DEVELOPMENT.md #5538
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5538 +/- ##
=======================================
Coverage 93.69% 93.69%
=======================================
Files 57 57
Lines 4391 4391
Branches 850 850
=======================================
Hits 4114 4114
Misses 277 277 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
|
||
| ## Reproducing issues | ||
|
|
||
| We recommend creating a folder named `sandbox` within this repo, and then using a child project within `sandbox` for each issue you want to repro. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually have a different repro flow. I keep a folder at ~/repos/repros as a sibling to ~/repos/mocha. It's a Git repo with a branch for each test case / reproduction. The publicly interesting ones get pushed to https://github.com/JoshuaKGoldberg/repros.
Alternately, sometimes I use ~/repos/mocha-examples to get starting reproductions. It's pretty handy.
I don't think we should recommend such a specific usage flow. Not every user is going to want this.
Proposal: how about making this more general, like saying having some folder somewhere?
| We recommend creating a folder named `sandbox` within this repo, and then using a child project within `sandbox` for each issue you want to repro. | ||
|
|
||
| `package.json` will have a reference to the local Mocha build and any options you need for your repro. | ||
| We recommend [`cross-env`](https://www.npmjs.com/package/cross-env) for applying the `DEBUG` environment variable to get detailed logs (via the [`debug`](https://www.npmjs.com/package/debug) package). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cross-env is only useful if you're on Windows. If you're on Mac or Linux then you can omit it.
Co-authored-by: Josh Goldberg ✨ <[email protected]>
|
Thanks for the review :) I'll come back to this after Christmas |
PR Checklist
status: accepting prsOverview
Yes, this PR is mostly for myself :D