You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repo can see one organization secret, PYPI_API_TOKEN. It cannot see LE_BOT_APP_ID or LE_BOT_PRIVATE_KEY, which every bot automation needs. As a result the existing automation here has
been failing since at least August. Grant the two required secrets, and the five optional ones.
Complexity: Low Target branch: Not applicable. This is an organization settings change, not a code change.
Context
The automations generate a token with actions/create-github-app-token, using LE_BOT_APP_ID and LE_BOT_PRIVATE_KEY. Neither is visible here, so the value arrives as an empty string and the first
step fails. Run 33453822106 shows it:
Error: The 'client-id' (or deprecated 'app-id') input must be set to a non-empty string.
If using a secret or variable, ensure it is available in this workflow context.
This predates the migration. It is not caused by learningequality/.github#88, and #353 does not fix
it. But the migration does widen it. Today three automations fail here. After #353 merges, twelve
fail, because every automation except resolve-bot-pr-threads starts by generating that token. The
failures would then look like the migration broke this repo.
Five further secrets are optional, and four automations use them:
An absent secret does not disable its automation. The caller forwards every key, so the value
arrives as an empty string and the step fails at run time.
All four sit behind the contributor check, which is true for anyone who is not a core team member.
A private repo therefore needs none of them, because no outside account can open a pull request or
comment there. This repo is public, so an outside contributor can arrive at any time.
The Change
Grant this repo visibility of seven organization secrets:
LE_BOT_APP_ID and LE_BOT_PRIVATE_KEY, which are required and fix the current failures.
The five in the table above, which the community automations need.
Run 33453822106 in this repo shows the current failure.
docs/automation.md in learningequality/.github lists every secret and says which are optional.
AI usage
I used Claude Code to audit organization secret visibility across the eight repos migrating to the
shared template, and to draft this issue from the result. I confirmed the secret list, traced the
failing run to the empty app-id input, checked the organization membership of the authors named
above, and edited the wording.
Overview
This repo can see one organization secret,
PYPI_API_TOKEN. It cannot seeLE_BOT_APP_IDorLE_BOT_PRIVATE_KEY, which every bot automation needs. As a result the existing automation here hasbeen failing since at least August. Grant the two required secrets, and the five optional ones.
Complexity: Low
Target branch: Not applicable. This is an organization settings change, not a code change.
Context
The automations generate a token with
actions/create-github-app-token, usingLE_BOT_APP_IDandLE_BOT_PRIVATE_KEY. Neither is visible here, so the value arrives as an empty string and the firststep fails. Run
33453822106shows it:This predates the migration. It is not caused by learningequality/.github#88, and #353 does not fix
it. But the migration does widen it. Today three automations fail here. After #353 merges, twelve
fail, because every automation except
resolve-bot-pr-threadsstarts by generating that token. Thefailures would then look like the migration broke this repo.
Five further secrets are optional, and four automations use them:
contributor-pr-replySLACK_COMMUNITY_NOTIFICATIONS_WEBHOOK_URLcontributor-issue-commentSLACK_WEBHOOK_URL,SLACK_COMMUNITY_NOTIFICATIONS_WEBHOOK_URLupdate-pr-spreadsheetCONTRIBUTIONS_SPREADSHEET_ID,CONTRIBUTIONS_SHEET_NAME,GH_UPLOADER_GCP_SA_CREDENTIALSunassign-inactive-issuesSLACK_COMMUNITY_NOTIFICATIONS_WEBHOOK_URLAn absent secret does not disable its automation. The caller forwards every key, so the value
arrives as an empty string and the step fails at run time.
All four sit behind the contributor check, which is true for anyone who is not a core team member.
A private repo therefore needs none of them, because no outside account can open a pull request or
comment there. This repo is public, so an outside contributor can arrive at any time.
The Change
Grant this repo visibility of seven organization secrets:
LE_BOT_APP_IDandLE_BOT_PRIVATE_KEY, which are required and fix the current failures.Out of Scope
Acceptance Criteria
call-pull-request-target.ymlrun succeeds on a new pull request, before Migrate to the shared automation.yml entry point #353merges.
failed step.
Testing
repos/learningequality/morango/actions/organization-secretsand confirm that all sevennames are listed.
succeeds, where it fails today.
step fails.
References
33453822106in this repo shows the current failure.docs/automation.mdinlearningequality/.githublists every secret and says which are optional.AI usage
I used Claude Code to audit organization secret visibility across the eight repos migrating to the
shared template, and to draft this issue from the result. I confirmed the secret list, traced the
failing run to the empty
app-idinput, checked the organization membership of the authors namedabove, and edited the wording.