abra catalogue generate silently drops uncommitted git changes #255

Closed
opened 2021-11-22 11:48:53 +00:00 by 3wordchant · 1 comment
Owner

Steps to reproduce

  1. Make some changes in a recipe repo, don't commit them
  2. Run abra catalogue generate <recipe>

Describe the expected behavior

Abra either bails out, or uses the uncommitted changes.

Describe the current behavior

Uncommitted git changes are dropped, effectively a git checkout / git reset --hard

Any idea how this might be fixed?

Similar approach to fixing it for app deploy?

Additional information

fdf4fc6

## Steps to reproduce 1. Make some changes in a recipe repo, don't commit them 2. Run `abra catalogue generate <recipe>` ## Describe the expected behavior Abra either bails out, or uses the uncommitted changes. ## Describe the current behavior Uncommitted git changes are dropped, effectively a `git checkout` / `git reset --hard` ## Any idea how this might be fixed? Similar approach to fixing it for `app deploy`? ## Additional information <!-- run "abra -v" on the command-line --> `fdf4fc6`
3wordchant added the
bug
abra
labels 2021-11-22 11:48:53 +00:00
Owner

Hopefully covered now! See bonus bug fix in dbf84b7640 and the actual fix in a18729bf98.

Hopefully covered now! See bonus bug fix in https://git.coopcloud.tech/coop-cloud/abra/commit/dbf84b7640b5b823e3ea5462b98837f760e18fcc and the actual fix in https://git.coopcloud.tech/coop-cloud/abra/commit/a18729bf98a8a9b610cfa16c9360c73d4d7dd934.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 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#255
No description provided.