[#120] Fix Broken CI Pipeline by Using GH Actions #121
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BrianBorge
force-pushed
the
120_fix_broken_ci_pipeline
branch
2 times, most recently
from
da6ca0f to
28b4510
Compare
|
@benliscio - Can I get access to settings or semaphore -- whatever I need to drop sempahore CI. I'm not sure which one I need to drop sempahore CI pipeline.
|
|
Failing specs are related but it's because #116 broke some of them and that's okay they will get fixed in a subsequent PR. The important part is that we are executing tests for ruby 2.3 again and soon ruby >= 3. |
BrianBorge
force-pushed
the
120_fix_broken_ci_pipeline
branch
from
fb28ca9 to
e694be5
Compare
benliscio
approved these changes
Sep 26, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
addresses #120