-
-
Notifications
You must be signed in to change notification settings - Fork 690
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
Re-enable ruby cck #960
Comments
It'll have to wait for the next release of |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. |
Bump @vincent-psarga |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. |
Bump @vincent-psarga |
We should move We can use the same approach as in Cucumber-JVM to copy over the golden messages: |
Reopening this again since it fails the build for some reason. We need to move this out of the monorepo and into cucumber-ruby. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. |
This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective. |
Done above |
It was disabled recently because it won't pass until cucumber-ruby is updated to use the latest messages. Let's wait to do this until all the open messages issues/PRs have landed on master and we've made a new monorepo release.
The text was updated successfully, but these errors were encountered: