Skip to content

ci: Migrate from opentelemetrybot to otelbot #1593

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 17, 2025
Merged

ci: Migrate from opentelemetrybot to otelbot #1593

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .github/workflows/release-please.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,15 @@ jobs:
name: Process Release
runs-on: ubuntu-latest
steps:
- uses: actions/create-github-app-token@df432ceedc7162793a195dd1713ff69aefc7379e # v2.0.6
id: otelbot-token
with:
app-id: ${{ vars.OTELBOT_APP_ID }}
private-key: ${{ secrets.OTELBOT_PRIVATE_KEY }}
- uses: googleapis/[email protected]
id: prepare
# with:
# token: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }}
# token: ${{ steps.otelbot-token.outputs.token }}
Copy link
Contributor

@kaylareopelle kaylareopelle Jul 17, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

@trask - Is this token a PAT for the otelbot?

I ask because currently, our release PRs (which are generated through a GitHub action) do not run the full CI automatically. In the past, we tried to use the OPENTELEMETRYBOT_GITHUB_TOKEN to help with this, but it didn't resolve the issue. We haven't tried it for a while.

Do you think we could use this token in our release workflows to get the CI to run when the automated PR opens?

Update Looking at open-telemetry/community#1549, it seems like this may solve our problem. I'll comment there.


outputs:
paths_released: ${{ steps.prepare.outputs.paths_released }}
Expand Down
4 changes: 2 additions & 2 deletions .toys/.data/releases.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,8 @@ main_branch: main
required_checks_timeout: 1200
required_checks: "^(ci|CI).*"
# Git user attached to commits for release pull requests.
git_user_name: OpenTelemetry Bot
git_user_email: 107717825+opentelemetrybot@users.noreply.github.com
git_user_name: otelbot
git_user_email: 197425009+otelbot@users.noreply.github.com

# Control the conventional commit linter.
commit_lint:
Expand Down
2 changes: 1 addition & 1 deletion release-please-config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
"release-type": "ruby",
"separate-pull-requests": false,
"sequential-calls": true,
"signoff": "OpenTelemetry Bot <107717825+opentelemetrybot@users.noreply.github.com>",
"signoff": "OpenTelemetry Bot <197425009+otelbot@users.noreply.github.com>",
"skip-github-release": false,
"tag-separator": " ",
"packages": {
Expand Down
Loading