Run nbconvert in travis and check for errors
Open
Nobody has claimed this yet.
to do
- Dominant language
- Jupyter Notebook
- Stars
- 200
- Forks
- 117
- PR merge metrics
- No merged PRs in 30d
Description
Running ```jupyter nbconvert``` on all the notebooks and re-executing every line is a good way to check they are all valid and changes haven't broken them.
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.
Research direction
Start by checking the repository's Travis configuration and the notebooks targeted by `jupyter nbconvert`. Configure the Travis run to execute nbconvert across all notebooks and verify failures are reported; done when the notebook validation runs in Travis and catches invalid or broken notebooks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100