Add zsh completion stub for nimbus
+2 -0contrib/completion/_nimbus.zsh
Registers a minimal _nimbus completion function so shells can discover subcommands without sourcing the full CLI.
contrib/completion/_nimbus.zsh+2
The next-gen git platform.
Comment on real lines. Stack dependent pulls. Triage next to the branch. Ship with GitHub-compatible CI and automation that fires on repository events. One surface, less tab debt.
#8
feat: include hidden flags in completion
6 files+24-0
Pull request #8
Add support for hidden flags in shell completion
This PR adds completion generation for the nimbus command across bash and zsh shells, with opt-in support for hidden flags via NIMBUS_COMPLETE_HIDDEN=1 environment variable.
The implementation introduces a new completion.go module that gates hidden flag visibility during completion generation. A seed GenBash() function in completion_gen.go provides bash completion output, while _nimbus_bash_complete completion is disabled by default for hidden flags; export NIMBUS_COMPLETE_HIDDEN=1 to reveal them.
The change is additive and backward-compatible — existing completion behavior stays intact. Test coverage validates that the TestHiddenFlagsMaskedByDefault function is callable.
Teach bash about hidden completion flags
+4 -0contrib/completion/_nimbus.bash
Bash completion now forwards NIMBUS_COMPLETE_HIDDEN when set, mirroring zsh behavior for scripting environments.
contrib/completion/_nimbus.bash+4
Generate completion metadata in build
+6 -0cmd/nimbus/completion_gen.go
Embeds a static table of commands and hidden flags into the binary so offline completion stays in sync with nimbus --help.
cmd/nimbus/completion_gen.go+6
Document hidden flag env vars
+3 -0docs/cli/completion.md
Operators can opt into exposing experimental flags during completion by exporting the documented variables.
docs/cli/completion.md+3
Wire completion tests
+5 -0tests/completion/hidden_test.go
Golden tests assert that hidden flags stay out of default completion output unless the env gate is on.
tests/completion/hidden_test.go+5
Changelog entry
+4 -0CHANGELOG.md
Release notes for completion improvements and the new env toggles.
CHANGELOG.md+4
1/61 of 6 files viewed this session
Plan, automate, and ship in one platform.
Collaborate on pull requests
Drafts and issues stay next to open PR rows, stacks stay grouped in order, and CI status shows on the list. Review and triage never leave the branch you are shipping.
PR review summary
Summarizes each new PR in one comment.
Scope
All repositories
Triggers
pr.opened
Automate on repo events
Install automations beside your repos. They run when real repository events fire—a PR opens, CI succeeds, a bot gets mentioned—with permissions you control and audit trails you can trace.
GitHub-compatible Actions
Run your existing .github/workflows YAML on Linux, ARM64, and macOS runners—with repo and org secrets, artifacts, and release publishing included.
Review, automate, and govern repos in one surface.
Keep diffs, issues, and automation on the same timeline as the code—without switching tabs or losing branch context inside Trylle.
Pull request #482
Harden JWT refresh + rotate signing keys
What changed
Security: shortens JWT refresh horizons and rotates signing assertions so webhook retries expose less surface.
Touch packages/api/src/auth/rotate.ts for verifier timing and backoff caps.
Rollout notes
Ops: staged flag flips default deny on legacy /v1/session/renew callers; dashboards tag cohorts still on long-lived cookies.
Expect a short spike in 401 charts until mobile bundles ship mid-week.
Guided pulls in Zen mode
Flip into a quieter lane—a narrative walk-through of what changed alongside the snippets that matter—so reviewers stay oriented without tab sprawl.
Activity
4refactor(docker): thread BuildKit mounts for CI secrets
7f3c9a218m agotrylle-bot left a review warning on Dockerfile4m ago
WarnDockerfile
L42trylle-bot4m ago
Potential secret in build context — Dockerfile promotes a bearer token via ENV; prefer BuildKit secrets (RUN --mount=type=secret) or CI-injected ephemeral creds before this lands on default.
- ENV DEPLOY_TOKEN="gh…" +# prefer: RUN --mount=type=secret…
Automations as early warning
Kick off bots on real repo events (`pr.opened`, `push`) to flag risky diffs—secrets drift, flaky touchpoints—right on the timeline where maintainers ship.
Direct access
| Member | Role | Actions |
|---|---|---|
SA sasha-ortizOwner Maintainers — default branch protections on | Admin | |
DE delivery-ci-botBot Service identity • restricted to merge queue writes | Write | |
EX external-contributorInvite revoked No longer meets workspace rules for this repo | — |
Draw clear repo boundaries
Pair Git identity with workspace rules—revoked invites, scoped actors, tightened merge surfaces—before noise escalates into accidental merges.
Review footer
PR #284 · Harden OAuth callback and refresh rotation
Assist, CI, and policy cues stay in one strip—reviewers skim signals before they decide, instead of bouncing through extra panels.
Assist · strong match
Confidence 87%
Checks passed · signed run
Scope locks on default branch
Last signal · 2m ago
Trust signals beside the proposal
Expose assist and provenance cues next to approvals—confidence hints grounded in tooling, not vibes—keeping humans decisive when tooling multiplies throughput.
Everything around the merge, built in.
The pieces teams usually bolt on—stacks, migration, releases, a review queue, a CLI—ship as part of the platform.
Stacked pull requests
Ship dependent branches as a stack. Pull lists keep stacks grouped in order, and the CLI creates, restacks, and submits them for you.
Migrate and mirror from GitHub
Import public or private repositories with history intact, and keep a push mirror in sync so the old remote stays alive while you switch.
Releases and artifacts
Cut releases with generated notes and uploaded assets, publish them from Actions-compatible APIs, and browse CI artifacts per run.
A queue for your reviews
One inbox for pulls waiting on you and the ones you authored—review state and CI status visible before you open a thread.
The try CLI
Repos, pulls, issues, stacks, CI, and automations from the terminal. JSON output built for scripts and agents, plus AI explain, draft, and diff helpers.
Runners for real matrices
Linux x86, ARM64, and macOS runners for Actions-compatible workflows, with verified commit signatures shown right on your history.
Free, Team, and Enterprise.
Seats unlock features and included usage. Pay-as-you-go wallet covers anything beyond your plan allowance.
Free
Solo org on review, issues, and repo-scoped automation—with monthly included usage.
$0per user / month
INCLUDED WITH FREE
- Unlimited repositories (fair use)
- 500 included CI minutes / month
- 200 included AI credits / month
- Pay-as-you-go wallet for usage beyond included
- 2 GB package & artifact store
- Collaborative review on branches and merges
- Issues, labels, mentions, and notifications
- Email & OAuth sign-in · community support
Team
Seat-based governance and higher included allowances for growing orgs.
$4per user / month
EVERYTHING IN FREE, PLUS
- 5,000 included CI minutes / month
- 2,000 included AI credits / month
- Wallet top-ups with optional auto-refill
- 75 GB package & artifact store
- Repository rules for branches, tags, and pushes
- Required reviewers and protected workflows
- Review automation and repeatable tasks
- Insights into activity and reviewer load
- Email support during business hours
Enterprise
Custom included allowances, SSO, audits, and procurement.
$18per user / month
EVERYTHING IN TEAM, PLUS
- Custom included CI minutes & AI credits
- Pay-as-you-go wallet with volume pricing
- 500 GB package & artifact store (pooled)
- Advanced repository rules & org-wide policy rollouts
- SAML single sign-on & advanced roles
- Audit-ready activity & export paths
- Hands-on onboarding and prioritized support
- Enterprise purchasing, SLA, and security questionnaire support
- Infrastructure options scoped to your program
Bring review home to your repository.
Migrate a repo from GitHub or push a new one, invite reviewers, and keep diffs, issues, and automation on the same timeline as the code.
Questions, answered.
Trylle is a git platform: pull requests, stacked branches, inline review, issues, releases, and GitHub-compatible Actions in one product. Built for teams that live in diffs.