publishing recipe version failed #290
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#290
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Describe the current behavior
made the tag but didn't commit the label change
Steps to reproduce
try running
abra recipe sync
and thenabra recipe release
. We did it with Loomio.Describe the expected behavior
Any idea how this might be fixed?
Additional information
abra version 0.3.0-alpha-de7054f
Just ran into this on Nextcloud.
recipe sync
didn't result in any file changes.On
recipe release
, initially I got this:and then after making some changes to tidy up labels, to give it some uncommitted changes:
hey @trav @3wordchant both recipes are using the old recipe labelling scheme and I think abra 0.3.x was a bit borked for this logic.
for nextcloud, i pushed
262d61cd0e
, now when I runabra recipe sync nextcloud
, the correct label is applied.for loomio, i pushed
0b65d69636
, sync now works also.i'm using the latest RC (
abra upgrade --rc
).if you wanna publish your recipe, you can pass
--publish
on therecipe release
command. Perhaps try without first and inspect the changes in~/.abra/catalogue
git repository to see if things are correct.then you can run
abra catalogue generate -p <recipe>
to publish to https://git.coopcloud.tech/coop-cloud/recipes so thatabra
can read it.also just hmu if you wanna do this together. we can also write documentation soon.