Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ RailsBump uses a few approaches to check whether a gem version is compatible wit

Since some gems have a lot of versions and each one needs to be checked against multiple Rails releases, this could get out of hand quickly. To minimize the amount of compatibility checks that need to be done, the gem versions are grouped by their dependencies first. If multiple versions (of the same gem or even of different gems) have the same dependencies, a single check is enough to determine whether all of them are compatible with a specific Rails release or not.

To actually perform the check, [GitHub Actions](https://github.com/features/actions) are used. For each check, a new branch is created in a [separate repository](https://github.com/railsbump/checker), which triggers a [workflow](https://github.com/railsbump/checker/blob/main/.github/workflows/check.yml) that essentially tries to run `bundle lock` and reports the result back to the RailsBump app via a [webhook](https://docs.github.com/en/developers/webhooks-and-events/about-webhooks).
To actually perform the check, we trigger a [GitHub Actions](https://github.com/features/actions) [workflow](https://github.com/railsbump/checker/blob/main/.github/workflows/check_bundler.yml) in a [separate repository](https://github.com/railsbump/checker) that tries to run `bundle install` and reports the result back to the RailsBump app via an API call.

## History

Expand Down