Dmitri Shuralyov

By now I'm very familiar with module mode. In order to implement support for it, I need to make decisions about what updates to display. In GOPATH mode, there was...

I've thought about this and picked some initial answers to start with. > display only the latest release or pre-release versions, or the latest pseudo-versions too For now, I'll do...

Here's a rough first draft (with some version information quickly added to the title):  It generally seems to work well, but it's pretty clear module mode will need some...

Thanks for the PR! I'll be able to review it the coming days. I have one commit that I've been testing locally before pushing to remote. Luckily, there'll be no...

I agree this information would be helpful to expose, especially when viewing specific commits other than the latest one on the main branch (something that gtdo lets users do). However,...

I understand what you're referring to. I can suggest two alternatives that would work: 1. Have the badges on the same line, space separated. It's consistent with the rendering as...

You're right, option 2 will give different behavior. It had to be done in some way. I considered it for some time: https://github.com/shurcooL/markdownfmt/blob/f9ece38f23b0150fcfaa82de98ec43ce0b98a83e/markdown/main.go#L456 But ended up choosing to go without...

I can reconsider the extension, but I won't be adding command-ling flags. I want to maintain the zero-configuration property of the formatting tool, just like `gofmt`. It will take me...

I'll be able to look at this more later, but I'm very interested in this! I've wanted to update `markdownfmt` to blackfriday v2; the only reason I haven't is because...

I've had many other priorities and haven't gotten around to this yet. As suggested in https://github.com/shurcooL/markdownfmt/pull/40#issuecomment-370029330, you can use @jsternberg's fork if you want a version of `markdownfmt` that uses...