)]}'
{
  "log": [
    {
      "commit": "008f9580cb1df44d70f1daa32b2122e10b7d8f79",
      "tree": "74ec1fe7013c16a11e3886424740a9b80411eee8",
      "parents": [
        "9236cce91da9ced563cf87dcde423dfbe18a1f1e"
      ],
      "author": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed Jun 04 16:26:15 2025 -0700"
      },
      "committer": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed Jun 04 16:26:52 2025 -0700"
      },
      "message": ".github: don\u0027t notify Discord from dev queue (sigh)"
    },
    {
      "commit": "837699bf55d27975e9e5b881b8794683bb1b10c8",
      "tree": "3aa7377ad7d441e10bfd0cf5e5f73a82de198764",
      "parents": [
        "c5848f3cb9753e94feddc04b8910b4ff113a458c"
      ],
      "author": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed May 28 18:58:17 2025 +0000"
      },
      "committer": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed May 28 12:01:29 2025 -0700"
      },
      "message": "github: fix Discord notification to handle multiple commits in queue push\n\nPreviously, commit queue pushes only notified about the final commit\ninstead of all commits being pushed to main. We now properly detect and\nnotify about all commits in a queue push in chronological order.\n\nChanges include:\n\n1. Enhanced push step in queue-main.yml and queue-dev.yml:\n   - Capture range of commits being pushed using git log origin/main..COMMIT_TO_PUSH\n   - Use --reverse flag to get commits in chronological order (oldest first)\n   - Store commit list in GITHUB_OUTPUT for notification step\n\n2. Updated Discord notification steps:\n   - Iterate through all commits in the push (not just the final one)\n   - Checkout each commit individually before calling discord_notify.py\n   - Send separate notification for each commit in correct chronological order\n\n3. Proper edge case handling:\n   - Single commit pushes: Works correctly (sends one notification)\n   - Empty pushes: Skips notification when no commits to notify about\n   - Formatted commits: Includes both original and formatting commits\n\nThe fix ensures that when developers push multiple commits to a queue branch\n(e.g., queue-main-username), Discord notifications are sent for each commit\nthat gets pushed to main, not just the latest one. Notifications appear in\nchronological order matching the actual commit sequence.\n\nCo-Authored-By: sketch \u003chello@sketch.dev\u003e\n\nChange-ID: s6a336eb2f945539fk"
    },
    {
      "commit": "6e4636006501be61b940388381cd75a8ad00e6b5",
      "tree": "39363c1c47111cbaf66eecd6b6e0274edbfa7b5c",
      "parents": [
        "77bac8c26324bad3c4b903a5321a2b0a078881ba"
      ],
      "author": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed May 28 18:10:59 2025 +0000"
      },
      "committer": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed May 28 11:33:56 2025 -0700"
      },
      "message": "github: add Discord notification to commit queue workflow\n\nThe Discord notification workflow was not triggering when commits were\npushed to main via the commit queue because GitHub Actions doesn\u0027t\ntrigger workflows when pushes are made using GITHUB_TOKEN (security\nfeature).\n\nThis fix adds Discord notification directly to the queue-main.yml\nworkflow after successful push to main, ensuring notifications are sent\nfor both direct pushes and commit queue pushes.\n\nChanges:\n- Add commit SHA capture in push step to track which commit was pushed\n- Add checkout step to ensure correct commit is available for git commands\n- Add Discord notification step using existing .github/scripts/discord_notify.py\n- Configure proper environment variables (DISCORD_WEBHOOK_FOR_COMMITS, GITHUB_SHA)\n\nThe existing discord-notify.yml workflow continues to work for direct\npushes to main, providing dual coverage for all scenarios.\n\nTested Discord notification script in test mode - generates proper embed\nwith commit message, author, and GitHub link.\n\nCo-Authored-By: sketch \u003chello@sketch.dev\u003e\n\nChange-ID: s94d86820e52726b5k\n"
    },
    {
      "commit": "936ba626345d9480698e7fced548224973b8a0a5",
      "tree": "04364304baefa8903aa23a846bfe4149b3010ea8",
      "parents": [
        "88c61bdd046f257e849aebf2fbe3be7c9c6f06ef"
      ],
      "author": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed Apr 30 20:53:21 2025 +0000"
      },
      "committer": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed Apr 30 17:19:01 2025 -0700"
      },
      "message": ".github/workflows: thread formatted HEAD commit to test sub-actions\n\nThread the commit SHA from the formatting job to the test jobs in GitHub workflows.\nThis ensures that when auto-formatting runs in the queue-main and queue-dev workflows,\ntests run against the newly formatted code rather than the original code.\n\nCo-Authored-By: sketch \u003chello@sketch.dev\u003e\n"
    },
    {
      "commit": "efda3961932b3c8d8fb169d9e043bc68c3dd1845",
      "tree": "2e5b037faaca7470ceca85d23219263045667bcd",
      "parents": [
        "db5e9b482194a801524a99af9fee06911147ff26"
      ],
      "author": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed Apr 30 13:09:42 2025 -0700"
      },
      "committer": {
        "name": "Josh Bleecher Snyder",
        "email": "josharian@gmail.com",
        "time": "Wed Apr 30 13:21:23 2025 -0700"
      },
      "message": ".github/workflows: add a dev queue for GitHub Actions hacking\n"
    }
  ]
}