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
org, repo = (ENV["GITHUB_REPOSITORY"]||"").split("/")
match_org, match_repo = (ENV["MATCH_REPOSITORY"]||"").split("/")
platform :ios do
lane :init_ci do
setup_ci
github_action(
api_token: ENV["GH_PAT"],
org: org,
repo: repo,
match_org: match_org,
match_repo: match_repo,
writable_deploy_key: true
)
end
my github PAT is set up for repo, workflow, and even admin privileges and is being accessed.
Was there a change to the github api? the "list_deploy_keys" is no longer a part of the github API documentation that the error is linking to
The text was updated successfully, but these errors were encountered:
I know its probably too late; but I had the same issue and was able to resolve this by verifying the following;
The account you've used to generate the GH_PAT access token on, needs to have rights to list deploy keys.
using GitHub CLI I was able to find out my owner account could list them, but the account I used for automation wasn't.
checking the documentation: repository-roles-for-an-organization turns out to do so, the account needs the Admin Role on your project repository where its trying to list the deploy keys.
(which I guess makes sense because a write deploy key could do the same)
TLDR;
give the account that owns the GH_PAT the admin role for the GITHUB_REPOSITORY.
I'm attempting to use fastlane match to manage my certs and I haven't been able to get it to work properly.
I have been following the instructions on your blog https://www.joshholtz.com/blog/2020/05/19/fastlane-plugin-for-setting-up-github-actions.html and have set everything up as instructed but when I run the action I get
I have checked and the org and repo variables are correct, my yml looks like this:
And the init_ci in my fastfile looks like this:
my github PAT is set up for repo, workflow, and even admin privileges and is being accessed.
Was there a change to the github api? the "list_deploy_keys" is no longer a part of the github API documentation that the error is linking to
The text was updated successfully, but these errors were encountered: