You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using forked GH Actions. Originaly it was made due security reasons, but we figured out that it takes to much effort to support them. So instead lets switch to upstream actions with specified version, example:
upsidr/merge-gatekeeper@v1.1.1
When PR will be ready we should ask repo admin (@atymchuk) to allow this particular versions in repo settings.
P.s. If you will find another percona-platform/* actions in our CI you can replace them as well.
Suggested solution
No response
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
So to get this clear, I should look for the upstream actions for all the percona-platform/* actions, and replace it with the ones I found. And this should be done for all the workflows?
I didn't get the repo settings part. Could you explain that? @artemgavrilov
@mintbomb27 Yes, we want to replace all forked actions with their upstreams in all workflows in this repo.
We have repo settings that allow only specific actions. So once you will create PR with discussed changes CI there will fail. Then we will update repo settings with specified actions versions (requires admin permissions, so we will ask someone who has it).
Description
We are using forked GH Actions. Originaly it was made due security reasons, but we figured out that it takes to much effort to support them. So instead lets switch to upstream actions with specified version, example:
When PR will be ready we should ask repo admin (@atymchuk) to allow this particular versions in repo settings.
P.s. If you will find another
percona-platform/*
actions in our CI you can replace them as well.Suggested solution
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: