What is the best practice for authenticating operations between repos in an organization ? (e.g. one repo does an environment protected automation that populates data in another repo)
I know PAT from a high-level member of the organization does the trick, but this looks like a workaround, not a solution.
Is there a way to create some sort of an organization-wide access token (similar to PATs), to be used as a secret for a GiHA workflow, but without attaching it to any member rather attaching it to the organization itself ?