Abra safety features wrt. unstaged commits on deploy #199

New Issue

decentral1se · 2021-10-12T10:28:13Z

decentral1se commented

2021-10-12 10:28:13 +00:00

Describe the current behavior

related feature request for abra - refuse to deploy if $user = f and the env file isn't committed and pushed

Steps to reproduce

Hacking!

Describe the expected behavior

abra is sensible because we are not.

Additional information

version: something

## Describe the current behavior > related feature request for abra - refuse to deploy if $user = f and the env file isn't committed and pushed ## Steps to reproduce Hacking! ## Describe the expected behavior `abra` is sensible because we are not. ## Additional information  - version: something

decentral1se added the

bug

abra

labels 2021-10-12 10:28:13 +00:00

decentral1se added this to the Beta release (software) project 2021-10-14 10:34:22 +00:00

decentral1se commented

2021-10-18 07:02:18 +00:00

Actually, as we learned, my sketchy Works For Me ™️ defaults mean that changes are silently force wiped out! I will add a check to bail out if we see live changes instead so folks can stash stuff or use chaos mode.

decentral1se commented

2021-10-18 07:31:28 +00:00

It will bail out unconditionally now if it see unstaged changes (except for Chaos Mode).

Not even --force will make it overwrite them without consent is the thinking now.

It will bail out unconditionally now if it see unstaged changes (except for Chaos Mode). Not even `--force` will make it overwrite them without consent is the thinking now.

decentral1se closed this issue

2021-10-18 07:31:31 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#199