Skip to content

chore: add Aztec Foundation CI bot hello workflow#23421

Open
AztecBot wants to merge 1 commit into
nextfrom
cb/foundation-ci-bot-hello
Open

chore: add Aztec Foundation CI bot hello workflow#23421
AztecBot wants to merge 1 commit into
nextfrom
cb/foundation-ci-bot-hello

Conversation

@AztecBot
Copy link
Copy Markdown
Collaborator

Summary

  • add a PR-triggered hello workflow on next to verify AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN
  • intentionally no workflow_dispatch; this proves the secret path through normal PR CI
  • the job only calls Slack auth.test and prints non-secret identity fields

Validation

  • static check: workflow contains pull_request, does not contain workflow_dispatch, and references AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN
  • local env check from claudebox host: AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN passes Slack auth.test for Aztec Foundation

@AztecBot AztecBot requested a review from charlielye as a code owner May 20, 2026 00:50
@AztecBot AztecBot changed the title ci: add Aztec Foundation CI bot hello workflow chore: add Aztec Foundation CI bot hello workflow May 20, 2026
@AztecBot AztecBot enabled auto-merge May 20, 2026 01:22
@AztecBot
Copy link
Copy Markdown
Collaborator Author

Status note for review: this PR is intentionally PR-triggered only (no workflow_dispatch) and the live PR CI proof is green.

Evidence:

Current blocker is only required review from @charlielye.

critesjosh added a commit that referenced this pull request May 20, 2026
The default SLACK_BOT_TOKEN bot is not in #docs-alerts. Switch the docs
CI scripts to AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN (added in #23421),
which has access to that channel, and plumb the secret through ci3.yml.
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.

1 participant