-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Mapping workflow_dispatch
inputs into the Expression inputs
context
#1363
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See errors details in artifact MegaLinter reports on CI Job page |
workflow_dispatch
inputs into the Expression inputs
context
Codecov Report
@@ Coverage Diff @@
## master #1363 +/- ##
==========================================
+ Coverage 57.50% 63.90% +6.39%
==========================================
Files 32 41 +9
Lines 4594 6452 +1858
==========================================
+ Hits 2642 4123 +1481
- Misses 1729 2034 +305
- Partials 223 295 +72
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
I'm not shure, but I believe that this change conflics #1345. This raises the question, which should be merged first? Other than that I want to tell you that github stores all {
"inputs": {
"required": "required input",
"boolean": "true"
}
} |
Yes they might conflict. If either one is merged, I'll rework the other. 😊 |
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.
Thank you for adding the missing code to assign the inputs context. You get my +1, even if the test doesn't exactly match githubs behavior.
You are right regarding the input types. We need to coerce them. |
This should reflect githubs behavior now as well |
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.
Looks good to me
@KnisterPeter this pull request is now in conflict 😩 |
This implements a test to check for `workflow_dispatch` inputs. This will be a prerequisite for implementing the inputs.
This changes adds the workflow_dispatch event inputs to the `inputs` context and maintaining the boolean type
6a5b1b1
15ee530
to
6a5b1b1
Compare
@KnisterPeter this pull request has failed checks 🛠 |
@KnisterPeter this pull request has failed checks 🛠 |
The PR checks are failing due to actions/hello-world-docker-action@778decc, rerun doesn't help. |
@KnisterPeter this pull request has failed checks 🛠 |
Oh I see. We are depending on code which is not managed by the act team and that did change. |
I did re-run while the CI indicates that two tests failed (https://github.com/nektos/act/actions/runs/3263285979/jobs/5362282276#step:6:33010) and both are fine locally. But anyway if the error lies in the external code I guess I will wait with this PR until its fixed. |
You would need to flush your docker image cache (some stale images with act in it's name) to observe this locally, act currently never rebuilds docker actions. The CI always needs to build all docker actions. |
Any chance this can get released soon? Looks like the last release was 19 days ago |
There is one usual release per month |
This changes adds the workflow_dispatch event inputs to the
inputs
context and maintaining the boolean type.