Alfonso Montero López

@azertylr: now that #56 is merged, you might want to tweak your Compose manifest by adding a `build` section which references this repo's URL and see if it works for...

@azertylr : Glad to know it's working for you and thanks for sharing your Docker Compose snippet. I think it'll make for a good usage example, once Docker usage it's...

Aside from the mentioned Emacs packages (which use `git config --global` shell calls), I've looked at my own `gitconfig` and found sections: `[tig]`: https://jonas.github.io/tig/doc/tigrc.5.html `[github]`: I guess it belongs to...

I guess so, @ahmet2mir, since loading configuration options it's an independent task/step for the program, independent of which protocol/source you use. Even more, as gitconfig is capable of complex configurations...

@q2w, @ayushmjain: ping. review would be much appreciated...

*If* any other configuration format were to be added, I'd rather vote for adding YAML. IMO, it's more widespread and more familiar to most users. Disclaimer: only based on my...

My preference for YAML was very conditional to the convenience of adding support for _any_ other format (notice the initial "If" on my comment). After reading @webknjaz response, I've learnt...

@kyu08 : As an intermediate step, it would be awesome just having a Github Action that would build a binary for direct download from the releases section.

I guess amd64 will be the most downloaded. Although maybe with the right Github Action is just a matter of listing build architectures. Not sure, thou, since I have no...

Not sure about the complexity, looks like a nice addition, as I'm tinkering with improving logging configuration (ie. via env vars) for a handful of legacy apps. Still figuring out...