Workflows triggered by github-copilot-agent no longer have access to secrets (Secret source: None) #177690
Replies: 3 comments 5 replies
-
|
I observed this same behavior change, where secrets were previously granted based on Actions secrets but are no longer. It looks like this alternative does allow providing secrets to copilot agent now, though it is per repo rather than allowing the flexibility of Actions secrets like before: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment#setting-environment-variables-in-copilots-environment |
Beta Was this translation helpful? Give feedback.
-
|
This behavior change is intentional — GitHub recently updated how secrets are handled for Copilot-triggered workflows for security reasons. 🔍 What changed Previously, workflows triggered by the github-copilot-agent had access to Actions secrets automatically. Secret source: None instead of Secret source: Actions ✅ Current workaround You can still provide secrets to the Copilot agent, but it must now be done per repository, not via global org-level secrets. Docs: In short: Set repository-level secrets directly under Settings → Secrets and variables → Actions. Copilot agents will have access only to those specific secrets. Organization-level secrets won’t be inherited for Copilot-triggered workflows anymore. GitHub tightened this access model to prevent accidental or malicious secret exposure from AI-generated or external triggers. The behavior aligns with how Actions handle workflows triggered by untrusted actors. 💡 Recommendation If you rely on org secrets, you’ll need to replicate critical ones at the repository level until GitHub provides a broader policy toggle or update. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe this can help: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Copilot Feature Area
Copilot Workspace
Body
Hello,
I've noticed a recent and consistent change in behavior for our GitHub Actions workflows that are triggered by pull requests from the github-copilot-agent.
The Issue:
Previously, our workflows triggered by the Copilot agent would run successfully with Secret source: Actions.
As of recently, the exact same workflow file, triggered by the exact same github-copilot-agent actor, now fails. The "Set up job" log for the new run shows Secret source: None. This causes all our CI steps that rely on secrets to fail.
Evidence (Replicated in a Sandbox):
To ensure this wasn't a configuration change in our main repository, I replicated this in a clean sandbox repo and can confirm the same change in behavior:
Old Run: https://github.com/talitahalboth/wip-tests/actions/runs/17793874537/job/50577000682
Set up joblogs shows: Secret source: ActionsNew Run : https://github.com/talitahalboth/wip-tests/actions/runs/18711615327/job/53361191849
Set up joblogs shows: Secret source: None(the new run also works since I'm not using secrets anywhere here.)
This strongly suggests a platform-level change in how GitHub now handles workflows initiated by the Copilot agent. It seems these PRs are now treated as "untrusted" by default, similar to a pull request from a third-party fork, which requires manual approval to access secrets.
My Questions:
Can anyone else confirm they are seeing this behavior?
Was this an intentional security change by GitHub, and if so, where was it announced?
What is the new, recommended "best practice" for running workflows on Copilot-generated PRs that require secrets?
Thanks for any insights!
Beta Was this translation helpful? Give feedback.
All reactions