[Feature request] Optional commit constraint per target
Hey,
We have thought about omitting the commit field selection on certain development targets. This would allow scientists to develop better because the specified branch would always be updated automatically. However, for production systems, especially if they are accessible from outside, a specific commit should still be specified, which must be explicitly updated in redeployment.
Could deploy targets be given an option whether to require a commit hash or not?
Thanks, Philip