GitHub Community
How to inherit secrets when reusing workflows in Github Actions #23107
-
|
It was recently posted on the Github changelog blog that it’s now possible to inherit secrets between workflows and I went to understand better how it works in the link at the end of the article (Reusing workflows - GitHub Docs). I tried to use it in a project that I’m working on in the same way as it’s explained in the documentation but it didn’t work. See the print below. I also tried using Can someone explain why it’s not working or what i’m doing wrong? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
|
The first one doesn’t work because you’re trying to call the reusable workflow in a step, which isn’t possible (that’s for custom actions). A reusable workflow must be called at the job level. Point three under Using inputs and secrets in a reusable workflow has an example. I notice it also says there:
I hope that doesn’t mean you can’t use that for workflows owned by the same personal account. 🤔 |
Beta Was this translation helpful? Give feedback.
-
It almost certainly means exactly that. Just create an organization. They’re free. I have a couple. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, now it’s working as expected. It was just a lack of attention. And about the concern of the repository being in an organization or a personal account, I didn’t have any issues with that. The final file version for future visitors: on:
push:
branches: [main]
jobs:
tests:
uses: ./.github/workflows/ci.yml
secrets: inherit
deploy:
runs-on: ubuntu-latest
needs: tests
steps:
- uses: actions/checkout@v3
- name: Deploy
run: echo 'DEPLOY NEW VERSION!' |
Beta Was this translation helpful? Give feedback.
-
|
You should better paste valid yaml for "future visitors" ;) |
Beta Was this translation helpful? Give feedback.
-
|
What does your reusable workflow look like? inheriting secrets seems so broken… Errors suggest I have to specify exact secrets, but documentation says I can inherit. feat: compose github actions by SgtPooki · Pull Request #128 · ipfs-shipyard/pinning-service-compliance · GitHub |
Beta Was this translation helpful? Give feedback.
-
|
Hopping onto the thread, a question about using It doesn't seem possible to achieve this, right? Is there any workaround? |
Beta Was this translation helpful? Give feedback.
-
|
That docs say Given how I'd imagine implementing this, I wouldn't expect what you're looking for to be supported. So the workaround is to just be explicit (which is probably better for people trying to read your workflows later anyway). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I think in the case where there are 3 secrets then being explicit doesn't hurt, but if there are 10 and only 1 has a different name then one might start scratching his head... but yes this might be en edge case. |
Beta Was this translation helpful? Give feedback.
-
|
As someone who regularly has to pick up after other people have left or deal w/ spelling inconsistencies, it's really helpful if people tie everything together by showing their dependencies. I much prefer that to the case where there's something magical going on where I change something in one place and it isn't remotely obvious that it's being used somewhere else... |
Beta Was this translation helpful? Give feedback.
The first one doesn’t work because you’re trying to call the reusable workflow in a step, which isn’t possible (that’s for custom actions). A reusable workflow must be called at the job level.
Point three under Using inputs and secrets in a reusable workflow has an example. I notice it also says there:
I hope that doesn’t mean you can’t use that for workflows owned by the same personal account. 🤔