leanprover / leanprover/lean-action
Add an `elan` input which controls if `lean-action` installs `elan`
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 45
- Forks
- 22
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 1
Description
The elan input can have similar semantics to the existing build, test, and lint inputs.
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
Inspect the existing build, test, and lint inputs and the entry point where lean-action installs dependencies. Add the analogous elan control so installation follows that input, then verify the action's behavior for enabled and disabled values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100