Skip to content

Aperture 0.6.0

Choose a tag to compare

View all tags
@Hankaws Hankaws released this 01 Nov 09:57
· 19 commits to main since this release
v0.6.0
554d5a5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Aperture Bot works more like a teammate. Star a main bot and it greets you on Next up with the work across all your repositories, most urgent first, each one click from the bot that looks after it. Reply to the bot without /aperture ("yes", "do the second one", "why?") and it follows the thread. Its daily brief, red CI and the pull requests it opens unasked can go to a Slack channel, and on Mondays the brief says what it did in the last seven days.

Automation on the Bot page turns on every bot's daily brief doing its top idea at once, one pull request per repository. The bot changes ship in Aperture Bot v1.8 (Hankaws/aperture-bot@v1).

Added

  • A main bot, as Grok has one. Star a bot on its profile and it leads your team: first in the roster, and the face of Next up, a new view on the Bot page that plans your work across every bot's repository, most urgent first (red CI's fix, pull requests the bots opened that wait for your review, a review's likely bugs, then the other ideas), each one click away and handed to the bot that looks after that repository. With a main bot, the page opens on Next up. (#170)
  • Aperture Bot posts to Slack. With "Post to Slack" on the Bot page (slack-webhook and a SLACK_WEBHOOK_URL secret), the daily brief (with the Monday digest), a red run it explained, and a pull request it opened without being asked are posted to a Slack channel too, each linking back to GitHub. Only a Slack webhook address is posted to, it is never logged, nothing from GitHub or the model can ping or link there, and Slack being down never fails a run. (#169)
  • Aperture Bot can follow its own threads, as Grok's bots do. With "Follow its own threads" on the Bot page (follow-threads: true), you reply to the bot without /aperture: "yes" or "do the second one" does that suggestion, as ticking it would, and anything else is answered with the reply it follows in mind, changing nothing. It follows only whoever it answered (anyone who can write, on threads it started), never a comment that @mentions someone, and never anyone who cannot write. (#168)
  • A weekly digest in Aperture Bot's daily brief: on Mondays the brief also says what the bot did in the last seven days (pull requests opened, merged or waiting, likely bugs caught, what it answered and checked), in the Bot page's own words, so it reaches you in GitHub's notifications without opening Aperture. It is counted from the bot's own replies, with no model call. (#167)
  • Automation on the Bot page: one switch turns on every bot's daily brief doing its top idea without asking, or turns it off again. It shows where each repository's brief stands, then opens one pull request per repository that needs it, on its bot workflow and keeping its other jobs; a repository whose schedule runs another job is left as it is, and a pull request from an earlier switch that is still open is shown rather than opened again. Needs Aperture Bot v1.7. (#166)

Every change, newest first: CHANGELOG.md

Assets 2
Loading