github action to check that the cookiecutter works
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, documentation, testing
Research direction
Start by locating the cookiecutter template, the generated package, its documentation, and the GitHub Actions configuration. Define the workflow around generating the package, running it without errors, and building the docs; done means all three checks run successfully in GitHub Actions.
Written by the indexing model from the issue text.
Description
could also check that the generated package runs without error and that the docs build properly.
- Dominant language
- Python
- Stars
- 41
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from matplotlib/matplotlib-extension-cookiecutter
-
pre-commit Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
MANIFEST.in Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in matplotlib/matplotlib-extension-cookiecutter
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100