You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an upstream release of the proto is made use a GitHub action to generate the Go code using this repos tooling and submit a PR for review. Additionally, have automation built that will make a release of this repo when a new tagged version is merged to main.
The text was updated successfully, but these errors were encountered:
To accommodate the wish to keep our code generation separate from the opentelemetry-proto repository I think this should just be accomplished by a scheduled workflow that checks for a new version tag, and updates to it to make a PR.
If there is any reasonable way to signal if a change has broken the go compatibility promises, I would schedule a workflow to check if main is still compatible with the last release.
When an upstream release of the proto is made use a GitHub action to generate the Go code using this repos tooling and submit a PR for review. Additionally, have automation built that will make a release of this repo when a new tagged version is merged to main.
The text was updated successfully, but these errors were encountered: