GitHub Community
GitHub Action - Cannot Read Action Repository Secrets #157452
-
Select Topic AreaBug BodyHello, I tried it in one repository, and it worked: I tried it in another repository (by my user and by a user who has permission to add secrets), and it failed: In both cases, the secret (with the name: "SLACK_WEBHOOK_URL") was added in the settings -> security -> Secrets and variables -> Actions, under "Repository secrets" (we also tried without underscores and it still didn't work). Any ideas? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
It either doesn't think that webhook secret exists, or it is empty, based on the error message. I know you have checked it, but let's check it one more time. In fact, just create a new secret called MYWEBHOOK and put the slack webhook in there, change your code, and see what happens. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mickeygousset, |
Beta Was this translation helpful? Give feedback.
-
|
@mickeygousset, yes, it worked from another repo.
|
Beta Was this translation helpful? Give feedback.
-
|
Hey! I noticed you mentioned that the secret (SLACK_WEBHOOK_URL) was added under "Repository secrets" in settings → security → Secrets and variables → Actions, which is the correct place for it to work. However, it sounds like someone else may have set it up for you, since you mentioned it was added by a user who has permission to add secrets. Did you create the secret directly yourself in the settings, or was it set up by someone else on your behalf? There could be a small mistake in how it was added, like a typo or it being set up in the wrong area. There are many places where secrets can be added, and it's easy to get confused. For example, it could have been added as a:
I'm using the Slack webhook in one of my YAMLs, and just for testing, I renamed the secret in my YAML to one that doesn't exist. I got the same error you're seeing in the failed workflow run: Are you verifying the name and location of the secret first-hand, or is it just passed along to you by someone else who said, "Yeah, that's how I set it up"? If someone else set it up for you and you didn't verify it first-hand, maybe they could send you screenshots of how they added it? Without being able to double-check myself, I'd question the assumption that the secret has the correct name, was created in the right place, and has the correct input. It's easy for small details to be overlooked, so it might be worth double-checking those to make sure everything is set up correctly. Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
|
@readytotest I was able to look at the screen, the one that added the secrets, and everything looks fine, that's why it is strange... |
Beta Was this translation helpful? Give feedback.
-
|
@shirady Thanks for the confirmation! I looked at the PR that failed and it was created from a fork. From what I found in the documentation this looks like the root cause.
Could you have someone with write access to the destination repo create the branch and PR directly in the destination repo, instead of from a fork? Hopefully that resolves the issue with the Slack webhook. Let me know how it goes! |
Beta Was this translation helpful? Give feedback.
-
|
We merged the PR and tested it after it merged, and it worked. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Happy to hear that it's working now for you! |
Beta Was this translation helpful? Give feedback.
@shirady Thanks for the confirmation! I looked at the PR that failed and it was created from a fork. From what I found in the documentation this looks like the root cause.
Could you have someone with write access to the destination repo create the branch and PR directly in the destination repo, instead of from a fork? Hopefully that resolves the issue with the Slack webhook. Let me know how it goes!