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
The idea would be to be able to use setup multiple command categories, like update-version, deploy which would replace (or be next to) the current command and when calling the build-chain, being able to select which command to use (update-version, deploy, current) current would remain the default command use.
other condition: upstream, downstream and merge are reserved keys and cannot be called directly
The text was updated successfully, but these errors were encountered:
In the pull-request config, we can set different build commands (https://github.com/kiegroup/build-chain-configuration-reader#build-configuration-section-structure):
The idea would be to be able to use setup multiple command categories, like
update-version
,deploy
which would replace (or be next to) thecurrent
command and when calling the build-chain, being able to select which command to use (update-version
,deploy
,current
)current
would remain the default command use.other condition:
upstream
,downstream
andmerge
are reserved keys and cannot be called directlyThe text was updated successfully, but these errors were encountered: