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 some workflows after merging a code (e.g. from trunk to a tags/stable tag), it's required to deploy these changes to the server (e.g. production or staging).
This can be implemented as follows:
add a per-repository (no global version) config setting called commit.deploy-command, which will store a Bash command that will do a deploy;
when a commit is performed (automatic after merge or manual) AND svn:mergeinfo property was changed AND commit.deploy-command config setting is specified, then execute it without buffering so that the user can see results in real-time.
The text was updated successfully, but these errors were encountered:
In some workflows after merging a code (e.g. from
trunk
to atags/stable
tag), it's required to deploy these changes to the server (e.g. production or staging).This can be implemented as follows:
commit.deploy-command
, which will store a Bash command that will do a deploy;svn:mergeinfo
property was changed ANDcommit.deploy-command
config setting is specified, then execute it without buffering so that the user can see results in real-time.The text was updated successfully, but these errors were encountered: