It would make sense that gddo will support versioned documentation.
On Tue, Mar 12, 2019 at 4:41 AM Sameer Ajmani wrote:
> Any of the above :-)
> On Mon, Mar 11, 2019 at 1:13 PM Eyal wrote:
>
>>
>>
>> On Sunday, March 10, 2019 at 12:10:23 AM UTC+2, Sameer Ajmani wrote:
>>>
>>> Very nice. As a p
Any of the above :-)
On Mon, Mar 11, 2019 at 1:13 PM Eyal wrote:
>
>
> On Sunday, March 10, 2019 at 12:10:23 AM UTC+2, Sameer Ajmani wrote:
>>
>> Very nice. As a point of interest, I wrote something similar for Go
>> packages inside Google called "writeme". It worked with multiple languages
>> (t
On Sunday, March 10, 2019 at 12:10:23 AM UTC+2, Sameer Ajmani wrote:
>
> Very nice. As a point of interest, I wrote something similar for Go
> packages inside Google called "writeme". It worked with multiple languages
> (the ones used inside Google), but had to be run manually. Your hook
> int
There is also Dave's https://github.com/davecheney/godoc2md, though
this is no longer maintained and intended for command line use.
On Fri, 2019-03-08 at 05:34 -0800, Eyal wrote:
> Hi
>
> I've created this Github App that automates the creation of readme
> files.
> It generates for Go project a r
Very nice. As a point of interest, I wrote something similar for Go
packages inside Google called "writeme". It worked with multiple languages
(the ones used inside Google), but had to be run manually. Your hook
integration is much nicer!
Have you thought about how module information might be inco
Hi
I've created this Github App that automates the creation of readme files.
It generates for Go project a readme up on the Go doc.
I think it will be useful because it removes the burden of maintaining two
documentation resources, and as a side effect, will result in improving the
go doc of pr
