To keep the grate project healthy and sustainable, we have made the decision to move from erikbra/grate to grate-devs/grate.

Please update your remote URLs to point to the new location:

Platform	Old location	New location
Github org	erikbra/grate	grate-devs/grate
NuGet	erikbra.grate	grate-devs.grate
DockerHub	erikbra/grate	no change

grate

SQL scripts migration runner

Example workflow runs

Below are examples on how to integrate grate in your workflow in different CI systems.

Build pipeline	Last run	Build definition
Github actions		/examples/github-actions/grate-workflow.yml
Azure DevOps		/examples/AzureDevops/azure-pipelines.yml

Goal

The goal of grate is to be largely backwards compatible with RoundhousE, which is an amazing tool. It is initiated by the main maintainer of RoundhousE for the last three years, please see this issue in the RoundhousE repo for details: https://github.com/chucknorris/roundhouse/issues/438.

While early versions of grate may not support every last RoundhousE feature, those features that are implemented should work identically, or with only very small changes. For detailed information see the migration docco.

Docs

Full documentation is available on the grate site.

Why the name grate?

grate is short for migrate. And it's also pronounced the same way as great, so, there you go.

Status

grate is catching up on RoundhousE features, there are a couple of features missing, they are documented in unit tests. But I've successfully replaced RoundhousE with grate in a 5-year-in-development folder of SQL scripts, without any issues.

Contributing

Please see CONTRIBUTING.md