himazawa

@bo-ku-ra the issue still exists tho. Because the arrows pointing to `child1` are straight. From your example, adding a link to another child will break anyway: ``` user: { shape:...

As already stated, semicolon are not super-easy to type with a non-ANSI layout. I really like zig, but having used languages without semicolons for the last ~7 years, going back...

Honestly I would prefer a release cycle based on conventional commits. For this purpose [release-please](https://github.com/googleapis/release-please) could be useful. We use `go-github` in production, having new major releases just for minor...

> we have never bumped the major release number without a breaking API change to my knowledge and we weren't proposing we do that, either. You are right, the current...

Any news on this PR? has been 4 months already in WIP. Due to the fact that this is needed to display thumbnails in selfhosted instances using self-signed certs I...

Yes I can look into it but looks like the issue is bigger since looks like `resp.NextPage` stays to 0 even if there are pages. Check this repro: ``` func...

Yea @gmlewis, I was looking at the same issue you linked. There is no way to paginate that endpoint using `ListOptions`. The doc doesn't seem so clear about it tho....

I don't think it will break anything, indeed the ambiguity is only trying to call `opts.Page` and `opts.PerPage` so just putting them explicitly shouldn't break anything, let's see