Issue #6474
closed
plugin_template generates a new directory that does not pass ci out of the box
Status:
CLOSED - CURRENTRELEASE
Description
This might not be the best experience for a new contributor.
There are only a few steps needed, so we could document them.
On the other hand, we could try to generate a plugin_template that passes out of the box.
I like this idea, newly generated plugin generally don't pass on the CI due to flake8, which somewhat discourage users to enable CI.
I'm in favor of having a CI permissive to flake8 errors than not having CI enabled.
So +1 to make easier for plugin writers to have a CI running just out of the box
- Triaged changed from No to Yes
- Sprint set to Sprint 70
- Sprint changed from Sprint 70 to Sprint 71
We decided, that that we want to improve the README in plugin_template to guide the user to the state, where the ci should be green.
- Status changed from NEW to POST
- Sprint changed from Sprint 71 to Sprint 72
- Sprint changed from Sprint 72 to Sprint 73
- Sprint changed from Sprint 73 to Sprint 74
- Sprint changed from Sprint 74 to Sprint 75
- Sprint changed from Sprint 75 to Sprint 76
- Sprint changed from Sprint 76 to Sprint 77
- Sprint changed from Sprint 77 to Sprint 78
- Sprint changed from Sprint 78 to Sprint 79
- Sprint changed from Sprint 79 to Sprint 80
- Sprint changed from Sprint 80 to Sprint 81
- Status changed from POST to MODIFIED
- Tags Plugin Template added
- Sprint/Milestone set to 3.8.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Cleanup README
fixes #6474 https://pulp.plan.io/issues/6474