feat: diff on release flow #375
No reviewers
Labels
No Label
bug
build
ci/cd
contributing
design
documentation
duplicate
enhancement
help wanted
invalid
meta
question
security
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#375
Loading…
Reference in New Issue
No description provided.
Delete Branch "diffing-release"
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?
See coop-cloud/organising#466.
Needs tests.Also, @yksflip (feedback welcome from all!) what do you think of this:
abra recipe upgrade <recipe>
now shows a diff at the endabra recipe sync <recipe>
now shows a diff at the endabra recipe release <recipe>
shows diff before prompting if new version is correctIs theSeems fine.recipe release
diff overkill now? I'm unsure.I've found an option that removes unstaged files from being counted in the new commit as per coop-cloud/organising#466 (comment) so we don't need to worry about rogue
blabla.txt
ending up in a release.bdb27bcd9e
to608a52ada9
608a52ada9
to7f7f7224c6
WIP: feat: diff on release flowto feat: diff on release flow