David Pordomingo
David Pordomingo
discovered at https://github.com/src-d/empathy-sessions/issues/37 _considering the old https://github.com/src-d/gitbase/issues/361#issuecomment-401838421, I'm not sure if you already discarded the interoperability with MySQL Workbench, so feel free to direct close if it makes no sense...
`go 1.13` has been released, and [our guide says](https://github.com/src-d/guide/blob/master/engineering/conventions/go.md#supported-go-versions) that >_our **applications** support only latest [stable](https://golang.org/dl/#stable) Go version_ `go 1.13` offers [error wrapping](https://golang.org/doc/go1.13#error_wrapping) (`errors.Is`, `errors.Wrap`...) For [error handling, our guide...
Considering the feedback given at [src-d/blogpull/176#issuecomment-356458445](https://github.com/src-d/blog/pull/176#issuecomment-356458445), it seems to be needed to improve the [continuous delivery for web sites](https://github.com/src-d/guide/blob/master/engineering/continuous-delivery.md) guide. It would be also great to link that doc in...
This PR documents the logging using GitHub and Google OAuth, as implemented by https://github.com/src-d/sourced-ui/pull/320. We could also consider if linking these docs from our main docs (also in GitBook). ---...
required by https://github.com/src-d/backlog/issues/1485 same as in https://github.com/src-d/sourced-ce/pull/263 and https://github.com/src-d/sourced-ce/pull/159 `bblfsh/bblfshd` has been updated to [v2.16.1](https://github.com/bblfsh/bblfshd/releases/tag/v2.16.1) in order to use the same logging level as the other components reading `LOG_LEVEL` environment...
caused by [#162::comment.r307650453](https://github.com/src-d/sourced-ce/pull/162#discussion_r307650453) >_[...] it may be nice to also return different return codes instead of using `1` for all of them._ This could be considered with #165 _Originally posted...
from https://github.com/src-d/sourced-ce/pull/162#discussion_r307696411 _disclaimer, I might be wrong because I didn't paid too much attention to the described problem; I just left this as a product of a discussion from https://github.com/src-d/sourced-ce/pull/162_...
_Originally posted by @EgorBu in https://github.com/src-d/sourced-ce/pull/115_ >_Like when you want to use `jupyter` - some kind of server application - you launch it, expose port, so external people can connect._
I commented on https://github.com/src-d/sourced-ce/commit/c9cdd13db5007d5ad07d1b87911c1b51bbc35dc4 from @vcoisne, about 10 different changes that could alter or damage our docs if not done on purpose. examples: - `CONTRIBUTING.md` and `LICENSING.md` moved outside of...
We could have an automated way to upgrade `sourced` once it has been locally installed. To update `sourced`, the steps to be (manually) done, are docmmented by https://docs.sourced.tech/community-edition/learn-more/faq-troubleshooting#how-can-i-update-my-version-of-source-d-ce (from @smacker...