Clément Delafargue
Clément Delafargue
In the example you gave, `--until` is silently ignored, and you have only `--after`, where non-termination is the expected behaviour
Indeed. For lines coming from the websocket connections, there is just a filter, but the stream is not closed
That'd be great Le mer. 11 avr. 2018 à 18:38, Hubert SABLONNIÈRE a écrit : > Should we use https://greenkeeper.io/ to keep our deps up to date? > > —...
Can you provide a concrete example of what you'd like?
Issue https://github.com/CleverCloud/clever-tools/issues/83 is all about removing the need for linking apps and being able to use name / ids everywhere. It's been thoroughly discussed and specified, so I think it'd...
For (2), clever link can also take an application id to remove ambiguity. Humans can use the name feature, but scripts should use the id as much as possible
For (4) the application polls the repository itself, and retries as long it's not created, so maybe it could just rely on that, instead of waiting? (maybe the repo poll...
I think 2. is the most satisfying way, as it reflects the API more closely and does not introduce behaviour specific to the CLI (it would be quite arbitrary, as...
Inky boi
What about `forbid if` or `reject if`? Or maybe `check none` in opposition to `check all`?