Automate code generation via CI

[masih]

Would it make sense to automate the code generated here by setting up a CI job that either runs periodically or watches the changes to the multicodec CSV file?

[mvdan]

I'd personally say "no", see #49 (comment)

[lidel]

I think there is existential risk of not updating library to follow changes to table.csv:

• See the changes which were "missed" and i had to manually sync them: feat: update ./multicodec/table.csv #71 🙈
• See how bad things can get if we dont ensure codes are in sync and dogfooded by our stack asap https://github.com/ipfs/go-cid/releases/tag/v0.2.0

We really can't afford running in blind here.

Desired state

See prior art in ipfs/ipfs-webui#2049 – we have a CI that runs once a week and if there are any changes, opens a PR + pings GUI team for review.

We want the same thing for this library:

1. Run once a week and see if git submodule init && git submodule update --remote && go generate produced any changes
2. IF there are changes, commit them to sync-table-csv branch, and open a PR against master (if PR already exists, force-push latest version)

[lidel]

@galargh would you or someone from IPDX be able to add this to your queue? 🙏