AlexsLemonade / AlexsLemonade/training-modules
GHA: Submit a PR with rendered and live versions of notebook upon merge to master
Open
automate all the things
- Dominant language
- HTML
- Stars
- 77
- Forks
- 35
- Avg merge
- 18h 38m
- Merged PRs (30d)
- 3
Description
Related to #296 and #299, which I may close in favor of this issue.
> We could check building with every pull requests to master, and submit a PR with rendered/live updates on merge to master?
_Originally posted by @jashapiro in https://github.com/AlexsLemonade/training-modules/pull/348#discussion_r579314508_
Contributor guide
Research direction
Start by reviewing related issues #296 and #299 and the discussion in PR #348. Determine how merges to master should build rendered and live notebook versions and open an update PR; done means the workflow reliably creates that PR with both versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, jupyter-notebook
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100