Hendrik Maus
Hendrik Maus
As a workaround, yes, but not on the long run. I would prefer to pin a specific commit sha over that.
Unfortunately I have nothing to show in public. Am Sonntag, 14. September 2014 schrieb Xavier Seignard : > Hi @etx https://github.com/etx, > > wow, nice project! > > Thanks for...
I think the actual parsing shouldn't be integrated with blueman. It is another build step in a pipeline before running blueman.
@castarco indeed, this is not a trivial thing to implement. I'd like to second your idea of splitting the feature into multiple smaller parts; some could even be merged while...
+1 is there any way to help?
Is this supported by the official API blueprint specs?
Nice. This is also really neat if you write blueprints to run through dredd for testing besides your main documentation.
Hey @hannobraun, I'd like to support you with your release process (including #57). I have built https://github.com/hendrikmaus/rust-workflows as a reference implementation to copy and hack on for one's own repositories....
Yes, let's tackle #57 first. We should be able to store the binaries on each workflow run, using the artifacts feature. That way, no release is needed to host them.