GitHub Community
-
Why are you starting this discussion?Question What GitHub Actions topic or product is this about?Workflow Configuration Discussion Detailsidk why mine workflow not reciveing secretes in worklfows |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
You should add your secrets to environment secrets, you'd for example have different secrets/variables set for development, staging, prod environment. If you're on the free github plan, organization-level secrets are not available for private repositories. They only work with public repos. additionally you'd have to configure repository access policy under: Organization Settings → Secrets and variables → Actions → Click on the secret → Check "Repository access"... |
Beta Was this translation helpful? Give feedback.
-
|
still not detect(i tested this by shifting some secrets in env secrets but even those not detected at all) 
and mine org all repo are public nothing private (free plan btw)
|
Beta Was this translation helpful? Give feedback.
-
|
I can see that now you are reading the secret but it fails because of github access token not having valid permissions. When you created a what i assume is "Fine-grained personal access tokens" You have to set it permissions from the error https://github.com/settings/personal-access-tokens/new |
Beta Was this translation helpful? Give feedback.
-
|
let me know any change in permission required in org as i created this few days ago |
Beta Was this translation helpful? Give feedback.
-
|
Managed to fix it? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I managed to fix it The issue was resolved after I changed pull_target_target to pull_target. idk how that solved it automatically, but things are working as expected now |
Beta Was this translation helpful? Give feedback.
You should add your secrets to environment secrets, you'd for example have different secrets/variables set for development, staging, prod environment.
If you're on the free github plan, organization-level secrets are not available for private repositories. They only work with public repos. additionally you'd have to configure repository access policy under: Organization Settings → Secrets and variables → Actions → Click on the secret → Check "Repository access"...