Skip to content

No way to track what changed between updates #154

Description

@SDcold

Development has picked up sharply lately. As of today, on main:

  • 38 of the 45 PRs ever merged landed in the last 30 days
  • 187 non-merge commits in the last 30 days, 566 in the last 90
  • 0 tags, 0 releases, no CHANGELOG.md

With that pace, there's currently no way for a user to answer "what changed since I last pulled?" short of reading git log. Since most people update in place, a change to a config key or a script silently alters their setup with no trace of what changed or why.

It came up recently with the colorgen script breaking on materialyoucolor >= 3: the fix landed in #135, but anyone who hit it in between had nothing to point at.

Keeping some form of record of what ships over time would help a lot here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions