Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

Tweak "is this a substantial change?" heuristic #15

Merged
merged 2 commits into from
Mar 20, 2024
Merged

Conversation

robinjam
Copy link
Contributor

We're currently nagging devs too much (3 of the 5 repos this bot is notifying us about don't have changes substantial enough to bother releasing). Let's tweak the heuristic we use to decide if a change is important enough to nag about:

  • Don't consider changes to the gemspec (because these are often just changes to dev dependencies)
  • Consider changes to the changelog (if a dev considers them important enough to include in the changelog then they're probably important enough to release)

* Don't consider changes to the gemspec (because these are often just
  changes to dev dependencies)
* Consider changes to the changelog (if a dev considers them important
  enough to include in the changelog then they're probably important
  enough to release)
This is a heuristic to decide if the changes since the previous version
are significant enough to nag the owners of the repo to cut a new
release, so let's introduce `change_is_significant?` to clarify this.
@robinjam robinjam merged commit 1e61bdf into main Mar 20, 2024
13 checks passed
@robinjam robinjam deleted the change-heuristic branch March 20, 2024 16:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants