Skip to content

Update the buildkite "New Build" link #550

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
crazytonyli merged 1 commit into from
Jul 15, 2026
+2 −2
Merged

Update the buildkite "New Build" link #550

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
2 changes: 1 addition & 1 deletion bin/release.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -274,7 +274,7 @@ print_publish_instructions() {
echo
print_status "${prefix}Next: trigger the Buildkite publish build."
echo
echo " 1. Open https://buildkite.com/automattic/gutenbergkit/builds/new"
echo " 1. Open https://buildkite.com/organizations/automattic/pipelines/gutenbergkit/builds/new"
echo " 2. Branch: trunk"
echo " 3. Commit: $sha"
echo " 4. Environment Variables: NEW_VERSION=$tag"
Expand Down
2 changes: 1 addition & 1 deletion docs/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ It does **not** create the git tag or the GitHub release — that's Step 2.

Step 1 prints the SHA of the version-bump commit it just pushed. Trigger a new Buildkite build with that SHA pinned:

1. Open <https://buildkite.com/automattic/gutenbergkit/builds/new>
1. Open <https://buildkite.com/organizations/automattic/pipelines/gutenbergkit/builds/new>
2. **Branch**: `trunk`
3. **Commit**: the SHA printed by Step 1
4. **Environment Variables**: `NEW_VERSION=vX.Y.Z`
Expand Down
Loading