-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CI job for testing against the starter repo #73
Conversation
@jagthedrummer How urgent is this? I would wait when #74 is resolved if possible (we're looking for solution with @kaspth) to be able to release next versions with green tests. |
@newstler not super urgent. I just figured that we should get this going sooner rather than later since we kept finding issues after a release instead of before. |
This make it so that the GitHub Actions CI pipeline will: * Checkout the starter repo. We'll look for a branch on the starter repo that matches the name of the branch being tested. If we can't find one we'll test against the `main` branch. * Checkout the `core` repo, also looking for a matching branch. * Alter the `Gemfile` in the starter repo to point to the local branch of `jbuilder-schema` and the `core` gems. * Run the Minitest suite of the starter repo * Run the Super Scaffolding suite of the starter repo
86caf02
to
7c3457e
Compare
@jagthedrummer Released this as v2.6.7 so should be good to check in BT gems without updating the minor version number there again. |
This make it so that the GitHub Actions CI pipeline will:
main
branch.core
repo, also looking for a matching branch.Gemfile
in the starter repo to point to the local branch ofjbuilder-schema
and thecore
gems.Run the Super Scaffolding suite of the starter repoEdit: I'm not sure it's useful to run the Super Scaffolding tests, so I'm skipping it for now.