+-------------------------------+------------ zenstruck ------------------+------------+------------+
| Repository                    | Latest Release | Status                 | Changelog? |    CI?     |
+-------------------------------+----------------+------------------------+------------+------------+
| zenstruck/phpmyadmin-server   | v1.7.0         | up to date             |     ✔      |     ✔      |
| zenstruck/schedule-bundle     | v1.5.0         | up to date             |     ✔      |     ✖      |
| zenstruck/foundry             | v1.24.1        | unreleased commits (1) |     ✔      |     ✔      |
| zenstruck/browser             | v1.2.0         | unreleased commits (4) |     ✔      |     ✖      |
| zenstruck/callback            | v1.5.0         | up to date             |     ✔      |     ✔      |
| zenstruck/mailer-test         | v1.1.0         | unreleased commits (1) |     ✔      | (disabled) |
| zenstruck/messenger-test      | v1.5.1         | up to date             |     ✔      |     ✖      |
| zenstruck/console-test        | v1.4.0         | up to date             |     ✔      |     ✖      |
| zenstruck/collection          | none           | no releases            |     ✖      |     ✖      |
| zenstruck/signed-url-bundle   | v0.1.0         | up to date             |     ✖      | (disabled) |
| zenstruck/console-extra       | v1.1.0         | up to date             |     ✔      |     ✖      |
| zenstruck/assert              | v1.2.0         | up to date             |     ✔      |     ✖      |
| zenstruck/changelog           | v1.5.2         | up to date             |     ✔      |     ✔      |
| zenstruck/twig-service-bundle | v1.0.0         | up to date             |     ✖      |     ✔      |
| zenstruck/uri                 | v2.2.1         | up to date             |     ✔      |     ✔      |
| zenstruck/redis               | v0.1.0         | unreleased commits (1) |     ✖      | (disabled) |
| zenstruck/class-metadata      | v1.0.1         | up to date             |     ✖      |     ✔      |
| zenstruck/dsn                 | v0.1.0         | unreleased commits (1) |     ✖      |     ✖      |
| zenstruck/dimension           | v0.1.0         | unreleased commits (5) |     ✖      |     ✔      |
| zenstruck/stream              | v1.0.0         | unreleased commits (1) |     ✖      |     ✔      |
| zenstruck/temp-file           | v1.0.0         | unreleased commits (1) |     ✖      |     ✔      |
+-------------------------------+----------------+------------------------+------------+------------+

Example Request for commit:

{
  repository(owner: "zenstruck", name: "foundry") {
    object(oid: "06b24d44fb76c0ab32f055ffb8a964de3a44925d") {
      ... on Commit {
        authors(last: 100) {
          edges {
            node {
              user {
                login
              }
              email
              name
            }
          }
        }
      }
    }
  }
}

Example Response:

{
  "data": {
    "repository": {
      "object": {
        "authors": {
          "edges": [
            {
              "node": {
                "user": {
                  "login": "jordisala1991"
                },
                "email": "[email protected]",
                "name": "Jordi Sala Morales"
              }
            },
            {
              "node": {
                "user": {
                  "login": "kbond"
                },
                "email": "[email protected]",
                "name": "Kevin Bond"
              }
            }
          ]
        }
      }
    }
  }
}

Get users:

$users = [];

foreach ($json['data']['repository']['object']['authors']['edges'] ?? [] as $item) {
    $users[] = $item['node']['user']['login'] ?? $item['node']['name'] ?? $item['node']['email'];
}

Currently, commands assume only one branch is maintained in a project: Github's default branch. For projects that maintain multiple branches (ie 1.x/2.x) this is a problem. Some general thoughts/ideas:

• add --branch= option to these commands
• error/ask if not set and multiple branches detected
• how to detect? probably if the source has multiple branches, ask
• will need to determine the proper --from #18 might help

1. List package names for organization
2. Get details about each package (ie https://repo.packagist.org/p2/zenstruck/foundry~dev.json)
3. Exclude abandoned packages (ie https://repo.packagist.org/p2/zenstruck/governator~dev.json)
4. Use source key to determine github repo (exclude if not github)
5. Fetch github details for each package and format same as #5