Skip to content

Resolve a few pain points found from running Herostratus at work - #183

Merged
Notgnoshi merged 8 commits into
mainfrom
ag/pain-points
Aug 18, 2026
Merged

Notgnoshi merged 8 commits into
mainfrom
ag/pain-points

Conversation

@Notgnoshi

Copy link
Copy Markdown
Owner

Closes #145.
Closes #182.

One of the things I've been seeing in my Herostratus instance I run at
$WORK is that the repositories in config.toml are constantly
re-arranging, which results in unnecessary changes polluting the diff in
the coordination repository.
This gives deterministic ordering at results in less run-to-run
differences in the updated cache data.
This removes a source of a diff that's always present between any two
runs, regardless of whether there were real changes.
Normally I'd shy away from updating everything in the Cargo manifest,
because I find it painful when consuming libraries that do the same (I
have to maintain projects at $WORK that have to maintain older stable
Rust toolchains, or have pinned dependencies that are incompatible). But
Herostratus is

1. an application
2. a hobby project
3. has a documented MSRV policy

so ... get rekt anyone who doesn't like it.
@Notgnoshi
Notgnoshi merged commit c3ca3bb into main Aug 18, 2026
6 checks passed
@Notgnoshi
Notgnoshi deleted the ag/pain-points branch August 18, 2026 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[repositories.<name>] config.toml fields constantly re-order Reduce size of H13 cache by allowing Rules to use MailmapResolver on finalize

1 participant