Skip to content

Conversation

@jack-berg
Copy link
Member

semantic-conventions-java prepare-release-branch workflow failed because it tried to create a branch restricted by the repo rulesets.

I added an exclusion of opentelemetrybot/**/* to get release back on track, but found that semantic-conventions-java references this repo's repository-settings.md as its source of truth.

It appears that this repo uses a release branch name pattern of otelbot/**/*, which is out of sync with opentelemetry-java and semantic-conventions-java. An alternative would be to update those two repos to use the name release branch naming pattern of opentelemetry-java-instrumentation.

@jack-berg jack-berg requested a review from a team as a code owner April 1, 2025 18:46
Copy link
Member

@trask trask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh ya I changed the branch name pattern when I changed from the opentelemetrybot GitHub user to the otelbot GitHub app. I need to update the other reps to use the otelbot GitHub app still.

See https://github.com/open-telemetry/community/blob/main/assets.md#otelbot

@trask
Copy link
Member

trask commented Apr 14, 2025

@jack-berg jack-berg closed this Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants