-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add auto-config
and build
inputs.
#61
Conversation
For a better idea of how these options are presented to users see the new |
@@ -26,15 +26,95 @@ jobs: | |||
- uses: leanprover/lean-action@v1-beta | |||
``` | |||
|
|||
## Configuring which features `lean-action` runs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@semorrison I don't think you need to go through the entire change set of this PR, however could you take a look at this new section of the README which outlines how users will configure lean-action
moving forward to confirm this is the right direction.
Note, the plan is to include lake lint
in the list of features which can be automatically configured (using lake check-lint
).
fb1df33
to
950b45b
Compare
`auto-config` allows users to specify if `lean-action` should use the Lake workspace to automatically decide which CI features to run. `build` allows users to specify if `lean-action` runs `lake build`. By default, `auto-config: true`. The `test` and `build` (and soon `lint`, see #46) inputs allow users to override the automatically configured behavior or configure `lean-action` when `auto-config: false`. `auto-config: true` is close to the previous default behavior, however there is a difference in the outcome of the `lake test` step. When users set `test: true` manually, `lean-action` must find tests with `lake check-test` and run `lake test` or it will fail (this was the previous behavior). However with `auto-config: true`, if `lake check-test` fails, `lean-action` will not run `lake test` and this won't cause `lean-action` to fail.
950b45b
to
411c31e
Compare
I am going to go ahead and merge this to keep things moving toward v1. We can revisit the inputs at any time. The behavior of |
auto-config
allows users to specify iflean-action
should use the Lake workspace to automatically decide which CI features to run.build
allows users to specify iflean-action
runslake build
.By default,
auto-config: true
.The
test
andbuild
(and soonlint
, see #46) inputs allow users to override the automatically configured behavior or configurelean-action
whenauto-config: false
.auto-config: true
is close to the previous default behavior, however there is a difference in the outcome of thelake test
step. When users settest: true
manually,lean-action
must find tests withlake check-test
and runlake test
or it will fail (this was the previous behavior). However withauto-config: true
, iflake check-test
fails,lean-action
will not runlake test
and this won't causelean-action
to fail.Closes #60, #53, and #30.