You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What should go into a PR template for this repository? I'd like to propose the following:
Radio button with options:
This PR adds a new tool descriptor
This PR updates a tool descriptor
This PR does something else
Check box: "I have read the CONTRIBUTING.md" document
Check box: "I am making this work available under the terms of the Apache License 2.0 (as per the LICENSE file)"
And then as a stop-gap for testing, perhaps we can ask that the test in the tests/ folder be run by the contributor and the cwltool output of running the test is appended as a comment in the PR. I'm not sure exactly how to work this but more importantly, what do others think about this? It will at least ensure that contributed tools are working.
Then on the last check box proposed above, how does that relate to the public domain donations issue? And do / should tool contributors retain copyright to their tools?
Finally, what else is there to add to such a template?
The text was updated successfully, but these errors were encountered:
What should go into a PR template for this repository? I'd like to propose the following:
This PR adds a new tool descriptor
This PR updates a tool descriptor
This PR does something else
And then as a stop-gap for testing, perhaps we can ask that the test in the
tests/
folder be run by the contributor and thecwltool
output of running the test is appended as a comment in the PR. I'm not sure exactly how to work this but more importantly, what do others think about this? It will at least ensure that contributed tools are working.Then on the last check box proposed above, how does that relate to the public domain donations issue? And do / should tool contributors retain copyright to their tools?
Finally, what else is there to add to such a template?
The text was updated successfully, but these errors were encountered: