Changelog and release notes · Autessa Status Page
Repository selection
Autessa Status Page lets you choose exactly which repositories feed the changelog. Settings lists the repositories in your GitHub organization with an on or off switch for each, a search box and Include all or Exclude all, and GitHub is reached through a read-only token stored as a sealed secret.
The problem it solves
Not every repository is a customer story
Most organizations have repositories customers never touch: infrastructure, internal tools, experiments, documentation of internal processes. Drafting from all of them buries the real changes in noise. Choosing the repositories that make up the product keeps drafts short and relevant.
What you get
- A switch for each repository: included or excluded.
- "4 of 68 repositories in your-org are included."
- Search repositories by name; Include these or Exclude these acts on the filtered set.
- Save changes is enabled only when something changed.
- Saving never overwrites the reviewers list, even if someone edited it at the same time.
- A "How the changelog works" card spells out the nightly draft, approval and reminder rules.
- GitHub access is a read-only token (pull requests and metadata) stored as a sealed secret and used only by the drafting tools.
How it works
How does repository selection work?
Open Settings
In Status Admin, under Setup.
Find the product repositories
Search by name, or start from Exclude all.
Switch them on
Turn on each repository whose changes customers can notice.
Save changes
Tonight's draft, Draft this day and the reviewer reminder all use the new list.
- Every night at 1:00 AM PacificA draft is written for the previous day from the repositories turned on.
- Every draft waits for a personNothing is published on its own.
- Every weekday at 4:30 PM PacificReviewers get an email with the drafts waiting.
- A day nobody approves never appearsDays with no merged pull requests get no entry.
Every option
Repository and connection settings
| Option | What it does |
|---|---|
| Repositories | One switch per repository in your organization. |
| Search | Filters the list by name. |
| Include all / Exclude all | Or Include these / Exclude these when filtered. |
| Save changes | Saves only the repository list, on top of the latest saved settings. |
| GitHub access | A read-only token with pull request and metadata read, stored as a sealed secret, limited to the GitHub API. |
| Used by | The nightly draft, Draft this day and the weekday reminder count. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| Staff in Status Admin | Include and exclude repositories. |
| Company admins | Store or replace the read-only GitHub token as a sealed secret. |
Connected
How it connects to the rest of Status Page
FAQ
Questions about repository selection
Does the changelog need write access to GitHub?
No. It uses a read-only token with pull request and metadata read access only.
Can I limit the changelog to some repositories?
Yes. Switch on only the repositories that make up your product in Settings.
Where is the GitHub token kept?
As a sealed Autessa secret that only the drafting tools can use, and only to call the GitHub API. It is never shown in Status Admin.
100% customizable, code and all
Make Autessa Status Page fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours