leanprover / leanprover/lean-action
expose sub-jobs of the main action
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 45
- Forks
- 22
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 1
Description
In some of my projects, I'd like to only install elan, or only install elan and get cache, without wanting to do any of the (potentially slow) later steps. For instance, if I have a multi-job flow which can run on different setups, the first one needs elan and mathlib cache, can build the oleans for the project, and the next job doesn't need to (slowly) get the cache again. As such, it would be helpful if this action gave me either
a) the option to control which setup / cooldown parts run
b) sub-actions (like the cache action does) which let me do only parts of it
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 reading the main action's setup and cooldown portions, then compare them with the existing cache action's sub-action interface. Determine which parts should be independently runnable and how a multi-job workflow would invoke them. Done means the requested setup steps can be selected without rerunning unnecessary later steps.
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
- Mostly clear
- Newbie friendliness
- 30/100