Jon Skeet

@duglin It looks like the recommended approach requires admin access: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository There's still a legacy approach I could use as documented here: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository Let me know if you'd like me...

@quartzmo: It's been a while since I created this issue; I created a PR for it at the time, but we decided not to create a new GHA... I think...

That PR is all green, so I think this really does need some attention after all.

Note that the librariangen-specific aspect will become obsolete when librariangen code moves to the librarian repo, but I'll leave this open for now in case it's symptomatic of a bigger...

Thanks @shollyman. Moving this to the google-cloud-go repo (and I'll edit the title appropriately).

> Use either Newtonsoft.Json or System.Text.Json to serialize the object to a JSON string. Basically, don't do that, I'm afraid. Protobuf has specific rules about how the JSON format is...

> Hi [@jskeet](https://github.com/jskeet), you memory profiling tools to ensure you are cleaning the resources correctly. I'm not quite sure what you mean. But all the methods above are executing successfully....

Hmm... while setting fields to null helps in my little test app, it's still flaky in my real application (which is doing rather more work). Currently I've got code to...

I'm afraid I'm unlikely to find time to add an icon any time soon, but we'll see.