leanprover / leanprover/lean-action
(DRAFT RFC) Add support for building leanblueprint to lean-action
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 45
- Forks
- 22
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 1
Description
Some projects rebuild the leanblueprint site when a new PR is merged into the main branch to keep the blueprint updated with the latest progress, e.g., this workflow from carleson.
I imagine there are a range of workflows for this CI step, so this may be difficult to support. But this seems like a nice feature to add to lean-action.
Contributor guide
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 reviewing the linked carleson workflow and the leanblueprint project workflow it invokes. Define which workflow patterns lean-action should support and what successful blueprint rebuilding after a main-branch PR merge must look like; the RFC should resolve the scope before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100