Add GitHub action to auto-rebase the migration branch #5315
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
In order to keep the
migration-deploy
branch up to date we are required to rebase it againstmain
every day. The current expectation is either for a developer to manually rebase the branch every morning, or for all developers to rebase the branch after merging a PR.This isn't ideal so I have attempted to create a GitHub action to perform this process automatically. It will run each time a PR is merged into this repo's
main
branch. Once we have fully migrated the API on to the DBT Platform, this action should be removed.You can test the action by doing the following:
chore/github-action-main
and merge itUpdate Migration Branch
chore/github-action-mig
and refresh. You should see the changes from your PR.Checklist
Has this branch been rebased on top of the current
main
branch?Explanation
The branch should not be stale or have conflicts at the time reviews are requested.
Is the CircleCI build passing?
General points
Other things to check
fixtures/test_data.yaml
is maintained when updating modelsSee docs/CONTRIBUTING.md for more guidelines.