Closed mjordan closed 7 years ago
@MarcusBarnes I'm thinking ahead a bit to how we want to describe this in a revised CONTRIBUTING.md. Can we call this new workflow the "testable" workflow, and call the other one the "smoketest" workflow, just to distinguish them? Can you think of other labels we might give them?
Also, reminder to also update the PR template as per https://github.com/MarcusBarnes/mik/pull/386#issuecomment-304357684.
@MarcusBarnes now that we've used the "testable" workflow in #386 and #390, are you comfortable officially adopting it? I guess by that I mean updating the CONTRIBUTING.md to describe it.
Let's officially adopt the testable workflow for appropriate pull-requests.
OK, I'll open a PR updating the CONTRIBUTING.md and PR template.
Addressed in pull-request https://github.com/MarcusBarnes/mik/pull/394 (merged with commit https://github.com/MarcusBarnes/mik/commit/174be7b2f986fa2a17b1f6f0b9d8b37a823fb61c).
As discussed in #370, we should introduce a new workflow that allows work that is covered by PHPUnit tests to be merged, at the discretion of the reviewer, without a full smoketest. The intent of this change is to reduce the burden on the person opening the PR to provide sample configuration and data to perform the smoke test. The proposed new workflow is:
Once we finalize this new workflow, we will need to update our CONTRIBUTING.md.