leanprover / leanprover/lean-action
Add a `nanoda-modules` input to specify modules to check by `nanoda`
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 45
- Forks
- 22
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 1
Description
The use case: a project where only part of it should be checked by nanoda. For example, a "clean" mathematical part (should be checked) and an algorithmic/native_decide-heavy part which cannot be check by nanoda. (specific repo which uses this division: WolframInstitute/UniversalityDB)
Proposal: new nanoda-modules input - a whitespace-separated list of modules. If this input is present, use it in the lean4export step in run_nanoda.sh instead of the default package/lean_lib name from lakefile.lean/lakefile.toml.
Related existing PR: https://github.com/leanprover/lean-action/pull/168 "fix: detect TOML lean_lib modules for nanoda"
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 with run_nanoda.sh and trace the lean4export step that currently uses the default package or lean_lib name from lakefile.lean or lakefile.toml. Check how action inputs are defined, then verify that a whitespace-separated nanoda-modules value selects only the requested modules while the existing default remains unchanged when it is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100