-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Allow inputs for workflow_calls #1845
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
Conversation
81cb660 to
0d4f719
Compare
|
@GuessWhoSamFoo this pull request has failed checks 🛠 |
Codecov Report
@@ Coverage Diff @@
## master #1845 +/- ##
==========================================
+ Coverage 61.22% 62.65% +1.42%
==========================================
Files 46 51 +5
Lines 7141 8209 +1068
==========================================
+ Hits 4372 5143 +771
- Misses 2462 2677 +215
- Partials 307 389 +82
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
d4d5250 to
b1c986b
Compare
cplee
left a comment
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.
Thanks!
|
@cplee Mergify seems to be unhappy with permissions |
|
@GuessWhoSamFoo Press "update branch" and it will continue. cplee should grant the workflow permission to mergify to prevent such weird issue. |
Fixes #1542
There's likely room to deduplicate some code in the future with generics once golang/go#48522 gets in a better spot since
WorkflowDispatchConfigandWorkflowCallConfigis iterating through inputs on shared fields. Embedding is also possible here although it would require a much larger refactor also not much gained imo.