You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to provide such functionality, a Composite Action can be used as a workaround (see, for instance, https://github.com/VUnit/vunit_action/blob/master/action.yml). However, that requires Action developers to duplicate the built-in functionality with regard to settings envvars, bindings, workdir, etc. inside the container.
This is partially related to #9049, because supporting inputs in the uses fields of Composite Actions would allow to use Container Steps.
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDProduct Feedback
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Container Actions are defined by an
action.yml
configuration file with fieldsruns: { using: 'docker', image: ... }
: https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action. Unfortunately, inputs cannot be used in fieldimage
, which prevents users from passing the image to be used as an argument.In order to provide such functionality, a Composite Action can be used as a workaround (see, for instance, https://github.com/VUnit/vunit_action/blob/master/action.yml). However, that requires Action developers to duplicate the built-in functionality with regard to settings envvars, bindings, workdir, etc. inside the container.
This is partially related to #9049, because supporting inputs in the
uses
fields of Composite Actions would allow to use Container Steps.Beta Was this translation helpful? Give feedback.
All reactions