fix: Throws an error when trying to deploy unstaged changes version #458
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "p4u1/abra:deploy-unstaged"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
My take on toolshed/organising#651
deploy-unstagedto fix: Throws an error when trying to deploy unstaged changes versionI'm not sure about this.
Similar to coop-cloud/abra#459, I don't think we should try to catch every specific situation with an error because we don't know what people are actually doing in all cases. E.g. in this message you assume "coworker" because you manually deal with a
$ABRA_DIR/.git
but for those that don't, this message could be confusing af?I'm starting to think we should added a field to
recipe.Recipe
which signals the unstaged changes instead of putting it in the actual hash string. Then we can continue just showing it on the deploy overview without blowing up the Git logic. I might try to add some additional visual triggers also. I'll try get a patch out for this.update: coop-cloud/abra#460
@ -67,6 +68,9 @@ func (r Recipe) EnsureExists() error {
// EnsureVersion checks whether a specific version exists for a recipe.
func (r Recipe) EnsureVersion(version string) (bool, error) {
if strings.Contains(version, "+ unstaged changes") {
%s/+ unstaged changes/+U/
ef95bce1e4/pkg/recipe/git.go (L250)
coop-cloud/abra#460
Pull request closed