Skip to content

fix(ci): use default GITHUB_TOKEN for collect-lime-results PR - #85

Merged
ccasanueva7 merged 1 commit into
developfrom
fix/collect-lime-results-token-2
May 23, 2026
Merged

fix(ci): use default GITHUB_TOKEN for collect-lime-results PR#85
ccasanueva7 merged 1 commit into
developfrom
fix/collect-lime-results-token-2

Conversation

@ccasanueva7

Copy link
Copy Markdown
Collaborator

Summary

Switches `peter-evans/create-pull-request` and `gh pr merge --auto` from `TESTBED_UTILS_TOKEN` (which doesn't exist in this repo) to the auto-provided `GITHUB_TOKEN`.

Why

First retry of the workflow with the PR-based flow failed: "Input 'token' not supplied". `TESTBED_UTILS_TOKEN` is the secret in lime-packages that lets that repo write into this one; here we don't have it, and we don't need a PAT — the workflow already declares `contents: write` and `pull-requests: write`, which the default GITHUB_TOKEN honours.

Test plan

  • Merge
  • Manually run "Collect lime-packages test results"
  • Verify the bot PR is created, auto-merges, and the report.xml files appear on develop

TESTBED_UTILS_TOKEN only exists in lime-packages (writing into this
repo). The collect workflow runs the other direction, so use the
auto-provided GITHUB_TOKEN, which already has pull-requests:write and
contents:write thanks to the permissions block.
@ccasanueva7
ccasanueva7 merged commit 89a62ac into develop May 23, 2026
1 check passed
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