-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
It would be nice to include a few paragraphs about development and the PR process. For example:
- How do you do a dry run of your branch? Do you need to plug in a device to test against for any changes? What is the expected behavior?
- How are tests written? How are they run? What's the minimum requirement for a satisfactory PR? Are including unit tests a requirement for a PR?
- Who can click a PR approval? Just @chalkers? Anyone involved in the project? Should you ever approve your own PR, even if it's possible?
- Is there any CI or other process oriented stuff developers need to be aware of?
- Is there anything missing from the official repo that a developer would need to add / get in order to fully test their branch? For example, any private configuration required?
- How should linting be done? What do you need to know about
jshintto properly lint your branches?
Metadata
Metadata
Assignees
Labels
No labels