Migrate CI from Buildkite to GitHub Actions

[Copilot]

Replaces the Buildkite pipeline with a minimal GitHub Actions workflow covering the same checks: gofmt formatting and go test -v -race ./....

Changes

• Added .github/workflows/ci.yml — runs on PRs and pushes to main; sets up Go 1.20, checks formatting, runs tests with race detector
• Removed .buildkite/ — pipeline definition, scripts, hooks, and PR config
• Updated catalog-info.yaml — removed the Buildkite pipeline Resource entry

Buildkite-specific steps (JUnit report generation and annotation) are not ported — they were CI infrastructure with no equivalent need in GitHub Actions.

Original prompt

Repository: elastic/bayeux

Task: Migrate the existing Buildkite pipeline to GitHub Actions.

Requirements:

• Replace the current Buildkite CI pipeline with a GitHub Actions workflow.
• Keep the GitHub Actions configuration as simple and minimal as possible while still covering the same essential checks currently done in Buildkite.
• Ensure the workflow runs on pull requests and on pushes to the default branch.
• For a Go project, include steps to:
  • check out the code
  • set up Go (use the repo’s Go version from go.mod if available, otherwise choose a reasonable stable version)
  • run formatting/linting if the Buildkite pipeline does so
  • run tests (go test ./...) and any other commands used in Buildkite.
• Remove/disable Buildkite configuration if appropriate (e.g., remove pipeline file or update documentation) to complete the migration.

Acceptance criteria:

• A new workflow exists under .github/workflows/ (e.g., ci.yml) that successfully runs the equivalent of the Buildkite pipeline.
• The workflow is minimal: avoid unnecessary matrix builds or extra actions unless needed.
• CI passes on existing tests.

Notes:

• Examine the existing Buildkite pipeline definition in the repo (likely .buildkite/pipeline.yml or similar) and port its steps.
• If there are scripts used by Buildkite, reuse them rather than duplicating logic.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Migrate the Buildkite pipeline to GitHub actions, GitHub actions should be as simple as possible

Assistant: I’ve kicked off the migration work and I’m waiting on your confirmation/approval prompt response to proceed with creating the GitHub Actions workflow and removing the Buildkite pipeline files.

This pull request was created from Copilot chat.

[v1v]

@copilot remove the bk pipeline definition from catalog-info.yaml

[Copilot]

@copilot remove the bk pipeline definition from catalog-info.yaml

Done — removed the Buildkite pipeline Resource entry from catalog-info.yaml in cacc163.

[fr4nc1sc0-r4m0n]

LGTM