Go packages in protocol/.github

[rvagg]

@marten-seemann we have 2 go packages in subdirectories this repo that we could get into the protocol/.github list. One catch is that we now have an auto-tag-and-release for each merged PR in this repo.

It’s not a big deal if we have patch releases triggered by the bot, but we could prevent them by including [ci skip] in the commit message.

We also use conventional-commits to build changelogs and determine semver bumps for each auto release, so it take the prefix: and use that to figure out patch/minor/major. Either like chore: or fix:, perhaps with a subsystem, chore(ci):, fix(ci): for descriptive changelog entries, would do the trick.

Do we have any flexibility in commit messages from the bot, or is that asking too much?

These packages are only for local codegen, not general consumption (at the moment anyway) so it's not a big deal if we leave them out because this is all too hard I think.

[marten-seemann]

We're currently using a static PR title sync: update CI config files for all PRs. Would that be something you could trigger on?

[rvagg]

@marten-seemann actually yeah, if it's consistently sync: then we can deal with it I think with #15