Open ItsGiantCookie opened 6 days ago
Hi @ItsGiantCookie, this should just be a matter of copy pasting the PAT value as a new org secret and providing access to your repo.
One thing that could explain your issue is if your workflow is triggered by a fork from a repo that is not part of your org (a third party contribution). As per GitHub security rules, third party forks don't have access to the repo/org secrets so this could explain why the value of the secret is blank.
Hi, I'm new to using Personal Access Tokens and Secrets and I'm having some issues with using my Personal Access Token in my Org. It is a fine-grained token, it's set as active in the Org itself and has the permission 'members' with read permission, which according to the short text, should give access to the Orgs teams and members info.
Is there a specific way to put a PAT into a Org-Secret to make it work?
This is the code I used.