Via graphQL how is object.commitUrl supposed to be used?

[edelauna]

Select Topic Area

Question

Body

Say for example I have the following query

query {
  repository(owner: "edelauna", name: "gpt-review") {
    object(expression: "HEAD:") {
      ... on Tree {
        entries {
          object {
            commitUrl
          }
        }
      }
    }
 }

All of the returned commitUrl result in 404 when navigated to via the browser even though the repository is public?

I thought maybe it required auth, but

curl -L \          
  -H "Accept: application/vnd.github+json" \         
  -H "Authorization: Bearer <TOKEN>" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
https://github.com/edelauna/gpt-review/commit/849ddff3b7ec917b5f4563e9a6d3ea63ea512a70

Returns Not Found - how is the commitUrl supposed to be used?

[Dimuthnilanjana]

Incorrect Object Type in Query:

Your query is navigating through object(expression: "HEAD:"), expecting a Tree, but commitUrl is not available at this level.
Instead, try querying Commit objects directly.

query {
repository(owner: "edelauna", name: "gpt-review") {
ref(qualifiedName: "refs/heads/main") {
target {
... on Commit {
history(first: 10) {
nodes {
commitUrl
}
}
}
}
}
}
}

This fetches the latest 10 commits and their URLs.

Incorrect commitUrl Resolution:

The commitUrl should follow this pattern:
bash
Copy
Edit
https://github.com/{owner}/{repo}/commit/{sha}
If the GraphQL API returns null or an incorrect URL, verify the repository and commit existence.
Authentication Issues:

Ensure the GitHub token has repo scope for private repositories or public_repo scope for public repositories.
Run:
sh
Copy
Edit
curl -H "Authorization: Bearer " https://api.github.com/repos/edelauna/gpt-review/commits
If it returns 404, your token may not have the required permissions.
Commit Visibility:

If the repository was recently made public, GitHub’s cache might still treat some resources as private. Try waiting a bit or clearing caches by pushing a new commit.
Next Steps
Try the corrected GraphQL query.
Ensure your token has the right permissions.
Manually construct the commit URL using SHA if necessary.

[Dimuthnilanjana]

Incorrect Object Type in Query:

Your query is navigating through object(expression: "HEAD:"), expecting a Tree, but commitUrl is not available at this level.
Instead, try querying Commit objects directly.

query {
repository(owner: "edelauna", name: "gpt-review") {
ref(qualifiedName: "refs/heads/main") {
target {
... on Commit {
history(first: 10) {
nodes {
commitUrl
}
}
}
}
}
}
}

This fetches the latest 10 commits and their URLs.

Incorrect commitUrl Resolution:

The commitUrl should follow this pattern:
bash
Copy
Edit
https://github.com/{owner}/{repo}/commit/{sha}
If the GraphQL API returns null or an incorrect URL, verify the repository and commit existence.
Authentication Issues:

Ensure the GitHub token has repo scope for private repositories or public_repo scope for public repositories.
Run:
sh
Copy
Edit
curl -H "Authorization: Bearer " https://api.github.com/repos/edelauna/gpt-review/commits
If it returns 404, your token may not have the required permissions.
Commit Visibility:

If the repository was recently made public, GitHub’s cache might still treat some resources as private. Try waiting a bit or clearing caches by pushing a new commit.
Next Steps
Try the corrected GraphQL query.
Ensure your token has the right permissions.
Manually construct the commit URL using SHA if necessary.

[edelauna]

Your query is navigating through object(expression: "HEAD:"), expecting a Tree, but commitUrl is not available at this level.

A commitUrl is most certainly available. Did you try my example graphql query? It will return a list of 10 or so objects all with what look like valid commitUrl URIs.