Add CI for jupyter notebook example `workflow_by_code.ipynb`
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Python
- Stars
- 48.7k
- Forks
- 7.7k
- PR merge metrics
- No merged PRs in 30d
Description
🌟 Feature Description
CI that it can't detect the errors in the report.
So I think it would be better to add such a check in our CI. (It may be some command like jupyter nbconvert workflow_by_code.ipynb)
Please refer to this comment.
https://github.com/microsoft/qlib/pull/1267#issuecomment-1230072848
Motivation
- Application scenario
- Related works (Papers, Github repos etc.):
- Any other relevant and important information:
Alternatives
Additional Notes
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 with the workflow_by_code.ipynb example and the CI configuration that runs repository checks; review the referenced pull request comment for context. Test whether a jupyter nbconvert-style check executes the notebook and exposes report errors. Done means CI reliably detects failures in this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100