[10:25] <Chipaca> good morning all
[10:38] <mup> Issue operator#358 opened: New configs added to a charm not available <Created by davigar15> <https://github.com/canonical/operator/issues/358>
[10:58] <facubatista> Muy buenos días a todos!
[14:41] <facubatista> Chipaca, jam, I splitted the "upload" branch again, as it was too big, here are just the "push bytes to storage" part: https://github.com/canonical/charmcraft/pull/75
[14:41] <mup> PR charmcraft#75: Support for pushing bytes to the Storage <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/75>
[14:45] <facubatista> Chipaca, jam, and is the "real Upload" one, after that one: https://github.com/canonical/charmcraft/pull/76
[14:45] <mup> PR charmcraft#76: Store upload <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/76>
[14:45] <facubatista> Chipaca, jam, I don't know how to flag 76 as "dependant of 75", as I used to do in Launchpad
[14:45]  * Chipaca reaches for his red pen of reviewing
[14:46] <jam> facubatista, afaict it isn't possible in github
[14:46] <facubatista> oh, crappy platforms
[14:46] <facubatista> :p
[14:46] <facubatista> I set 76 as "draft"
[14:50] <Chipaca> facubatista: what I usually do is just say "this builds on #<x>" and provide a link to the diff between x and y
[14:51] <Chipaca> so the reviewer doesn't have to do that by hand :)
[14:52] <facubatista> Chipaca, ideally, reviewers will focus on 75, and then will go to 76 after I land 75 (maybe with changes), update everything and let everybody knows; I just push 76 in advance "for context", if needed
[14:52] <Chipaca> k