Discussions related to GitHub Actions
I’m going to guess that your secrets are being stripped from the
python3 scripts/pipeline/upload_file_to_s3.py ... command and therefore missing args. You probably want to use environment variables that are set from secrets rather than just index based args…but again, just a guess
Hey, does anyone have experience with reusing github actions/workflows on multiple private repositories in a microservice architecture and would like to maybe share how you are doing it or some possible solutions? The most important things are:
• Repo containing the reusable actions/workflows needs to be private.
• Service repos should reference the reusable actions/workflows repo (not distribute workflows) So far I have tested out: Reusable workflows: would be very nice but it requires the reusable workflow repo to be public or internal (we don’t have enterprise github) Composite actions: works but some requires some additional checkout boilerplate when referencing a private repo.
waiting on https://github.com/github/roadmap/issues/98
Summary This feature enables you to reuse an entire workflow as if it were an action. Instead of copying and pasting workflow definitions across repositories, you can reference an existing workflow…
it supposed to be this quarter (but was already bumped from Q1 -> Q2 -> Q3 -> Q4, so might be bumped again)
@Darren Cunningham but its out in beta right?
news to me if so, but very well could be
oh the first link you provided
Did test it out here the other day, works well if the workflows are in a public repo
the example at the bottom looks like it would work with a private repo
I’m assuming that because it’s passing the secret token
I think that’s just passing in a secret token, not necessarily a github token.
I’m hoping that’s just limitations of the beta because that doesn’t sound like it’s adding any value in it’s current state