Marco Franssen

I used mitm proxy and this is what I intercepted. ```json { "query": "query($owner:String!$repoCursor:String){organization(login: $owner){repositories(first: 100, after: $repoCursor){totalCount,pageInfo{hasNextPage,endCursor},nodes{id,name,description,url,sshUrl,owner{login},isPrivate,createdAt,updatedAt,pushedAt,repositoryTopics(first: 25){nodes{topic{name},resourcePath}},collaborators(first: 15){totalCount,pageInfo{hasNextPage,endCursor},nodes{name,login,avatarUrl}}}}}}", "variables": { "owner": "philips-labs", "repoCursor": null } } ``` Cleaning...

Let me check that. How should I deal with that partial response from the lib if that is the case? What would you recommend?

You where right, ```json "errors": [ { "locations": [ { "column": 307, "line": 1 } ], "message": "Must have push access to view repository collaborators.", "path": [ "organization", "repositories", "nodes",...

It would indeed be great if we could do type assertions on the error to make a decision on how to continue. I can confirm it is a bug in...

FYI: Following is a workarround for the error by skipping archived repositories. ```graphql query($query:String!$repoCursor:String) { repos: search(query: $query, type: REPOSITORY first:100 after: $repoCursor) { repositoryCount pageInfo { hasNextPage, endCursor },...

Is there any update on this one? Like a revamp on how to deal with the errors from this library.

@vartanbeno any clue if this was an intended action from your side causing this issue for consumers of the library, or if this is a compromise in the library? Would...

Nice you guys are experiencing same issue. Would be great to have this resolved. @Hardtack do you think this can be done in short timeframe?

Probably this is the root cause https://github.com/terraform-docs/gh-actions/issues/50

For now I workarround the issue as following: ``` - name: Debug run: | ls -lha .git ls -lha .git/objects - name: Update module docs uses: terraform-docs/[email protected] with: working-dir: examples/${{...