Skip to content

OneCorp 0.1.5

Choose a tag to compare

@github-actions github-actions released this 11 Nov 05:48
· 181 commits to main since this release

Faster tickets, readable logs, and employees who ask instead of getting stuck.

Added

  • Discard work you don't want, from its review in the Inbox or on the ticket. The pull request is closed, the branch deleted, and the ticket goes back to the backlog to start again or delete.
  • An employee who needs a command they can't run asks for it in your Inbox, like xcodegen generate with the reason. Allow it and the whole team can run it in that repo, and the ticket picks back up. Git, root and pull request commands are never asked: OneCorp handles those.

Changed

  • Commits are yours by default once git knows your name and email. "As your team" is still one click away in Settings.
  • Pull requests end with a small signature: who did it, at which company, made with OneCorp. Choose Plain in Settings for none.
  • Inbox cards keep all their actions on one row, and summaries show code as code.
  • Run logs show what employees say in full, and whole commands and errors, wrapped under themselves instead of cut to one line.
  • The Repos section in Settings is calmer: a card per repo with its commands, Add a repo at the top, and shorter paths.
  • Long questions, wiki proposals and review summaries in the Inbox show a few lines, with Show all for the rest.
  • Every employee knows how OneCorp works: tickets live in OneCorp, OneCorp does the git work and decides what they can run.
  • Each repo's commands in Settings are now a list you can edit one by one: remove one with ×, or type and press Enter to add one. Pasting a list from a Claude Code settings file works, so Bash(make build:*) becomes make build.
  • Employees know OneCorp decides which commands they can run. They no longer ask you to create .claude/settings.json.

Fixed

  • A review no longer shows other people's merged work as part of the ticket when your local main is behind GitHub.
  • Run logs show code as code, and long temporary paths as just the file name.
  • Tickets in Rust repos stop rebuilding everything from scratch. A new ticket reuses the builds already in your checkout, cloned instantly on your Mac's disk.
  • A docs-only change no longer runs the full build and test suite. Employees run the checks that cover what they changed.
  • A long command in a run log shows "still running, 3 min" instead of looking stuck.
  • Asked in chat about the ticket they're on, employees see their latest steps and their worktree, so they no longer say they haven't changed anything when they have.
  • Wiki writing now saves and completes after a retry or usage-limit resume. Older wiki drafts stuck in review show the document and a Save wiki action instead of asking to merge a nonexistent branch. Completed wiki tasks link to the wiki; plan actions say they start a plan.