This kind of query isn’t something that the GraphQL API is designed to be able to give you at this point. In theory, if you’re certain that tag-x is an ancestor of branch-y, and you have the commit hash of tag-x, then you could go from the Commit object pointed to by branch-y and paginate through all commits (using the history connection) until you find the commit hash you’re looking for. You could also use the since parameter on the history connection to prevent you from overwalking. But that doesn’t solve for the case where y is the ancestor of x or that x and y are not proper ancestors of one or the other.

For now, using git itself is probably the best way to get at the information you’re looking for.

I hope that helps!

Thanks @lee-dohm for the helpful response! In truth, I’m only ever concerned with the master branch, and reality is that I need to see a commit list from the last release to the current point in time, as a new release is about to be generated.  So even if am just getting a list of commits up to the last tag, or list of commits up to the last release that would be enough. Is that possible with the “Release” or “Tag” and … on Commit fragment? I’m just learning GraphQl (first couple of days) so forgive the ignorance. 

Even if there was a way for me to list a bunch of commits, and discern that one of them was tagged, that would be enough, but I can’t seem to get that info just from “Commit” history.

@lee-dohm This is truly helpful.  I made it a little more dynamic by doing this:

{
  repository(owner: "CoolCompany", name: "awesome-ui") {
    releases(last: 1) {
      edges{
        node{
          tagName
          createdAt
        }
      }
    }
  }
}

Then I can use the createdAt you suggested in the same way and get my commit list since the last release. I really appreciate the help! It’s too bad I couldn’t do this all in a single query but it took me 3 requests with the v3 rest API so it’s still an improvement and the filtering logic is much easier now. Thank you!

You’re welcome 😀

One other thing to note is that you don’t need to do edges immediately followed by node in your queries unless you’re getting the pageInfo or totalCount from the edges connection. If you just want the stuff in node (as it appears you do in your query), it can be simplified to:

{
  repository(owner: "CoolCompany", name: "awesome-ui") {
    releases(last: 1) {
      nodes {
        tagName
        createdAt
      }
    }
  }
}

I hope that helps!

I’m curious how I would know what is the previous release. E.g. in one repo I have v1.1.0-beta3, v1.1.1, v1.1.0-beta4.
The github UI knows that the changelog for the first is v1.1.0-beta3..v1.1.0-beta4, but how I do know that from the GraphQL response?
I could do a “human-sort” on the release names, but that wouldn’t be guaranteed to work always.

Here’s the query (roughly):

...
releases(first: 100) {
      edges {
        node {
          name
          publishedAt
        }
      }
    }
...

Here’s the result:

          {
            "node": {
              "name": "v1.1.0-beta.3",
              "publishedAt": "2020-12-15T06:16:07Z"
            }
          },
          {
            "node": {
              "name": "v1.1.1",
              "publishedAt": "2020-12-15T07:03:35Z"
            }
          },
          {
            "node": {
              "name": "v1.1.0-beta.4",
              "publishedAt": "2021-04-07T13:23:00Z"
            }
          },