Buildkite: post docs-build-pr GitHub status from a follow-up step

[reakaleek]

Why

• Long docs-build-pr jobs expire VAULT_GITHUB_TOKEN before pre-exit posts the final GitHub status
• GitHub then stays pending while the Buildkite build is already green

What

• Upload a short follow-up step from pre-exit to post the final GitHub status with a fresh token
• Fail the status step when GitHub rejects the POST

Notes

• The uploaded step checks out the repo so the status script is on disk
• The step key includes BUILDKITE_JOB_ID so a UI retry of build-pr can post status again

Made with Cursor

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}