Skip to content

explicitly state that unit tests are required #207

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

Merged
merged 1 commit into from
Jun 4, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion WORKFLOW.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,9 @@ experienced contributors will help it through all 5 steps.
people involved in prior steps of the workflow. Other contributors (not
explicitly invited) are encouraged to provide reviews and suggestions as
well. Iterate until all (or most) participants are on the same page.
We can merge when there is vast majority approval of the PR.
A merge is permitted if there are unit tests for a majority of the possible
calling scenarios (with or without optional arguments, with arguments that
trigger an error) and if there is vast majority approval of the PR.

5. **Release**: Moving from experimental to release. The experimental
"namespace" contains new functionality together with its specification. In
Expand Down