[00:01] <nacc> looks like it, waited a bit annd it worked fie
[17:22] <nacc> true/false: it is not currently possible in the LP web UI to ask that a snap built by LP get published in a branch?
[17:32] <dobey> as in commit a built .snap package into a repository as a file?
[17:33] <nacc> dobey: as in, i have a snap recipe to build a snap from a Git repository. But I would like a specific Git branch to get published as a specific snap branch
[17:33] <nacc> dobey: I see tracks and channels in the web UI, but not branches
[17:35] <nacc> dobey: and while track is free-form, it goes track/risk/branch, so I can't specify the branch in the track (afaict)
[17:45] <cjwatson> nacc: true at present
[17:45] <cjwatson> nacc: you can always build it somewhere else and then use snapcraft release to stuff it into a branch of course
[17:45] <cjwatson> (not so automatic though)
[17:53] <nacc> cjwatson: yep, that's what i'm going to do
[17:53] <nacc> cjwatson: is that planned? i have lots of pending MPs and it'd be nice to ask people to test a snap of git-ubuntu built from my branch
[20:22] <cjwatson> nacc: not at present, and there are some policy concerns around it (e.g., branches only exist for stable and we want to discourage auto-builds into stable); not necessarily insurmountable but it would need discussion
[20:22] <nacc> cjwatson: ack, thanks
[20:23] <nacc> cjwatson: hrm, i am able to branch any risk level, btw
[20:23] <nacc> (that was a snapcraft change, it looks like, by the forum history)
[20:26] <cjwatson> nacc: last I checked the store enforced this; haven't checked super-recently
[20:28] <cjwatson> nacc: oh right, changed in the store in June apparently
[20:29] <cjwatson> so we could probably change that without a huge amount of work, but I should talk to some folks.  file a bug?
[20:55] <nacc> cjwatson: will do
[21:02] <nacc> cjwatson: LP: #1725481
[22:04] <cjwatson> thanks
[22:09] <nacc> cjwatson: np, thank you!