Issue with "secrets-sync-action" in internal repositories
Marouane-Belbouhali opened this issue · comments
Previously, we utilized the "secrets-sync-action" to synchronize secrets between repositories. Up until July 12th, the action was registered as "google/secret-sync-action." After that date, the organization was changed to "jpoehnelt/secret-sync-action."
Unfortunately, our workflow is currently nonfunctional, as the action can no longer be employed in our repository. It appears that our organization has imposed restrictions on the actions that can be invoked from workflows.
Has anyone managed to solve this issue?
@Marouane-Belbouhali You can check the Action permissions in the settings of your repository. Alternatively, you can fork the action to your own organization.