Run CI against rails/master #896
Merged
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
|
Ironically, this works even though https://github.com/airblade/paper_trail/blob/6411ab1ce6f661075092d7597d32e4c1f9eae7ff/paper_trail.gemspec#L27 is present because |
sgrif
force-pushed
the
sg-run-master-on-ci
branch
from
43bc86c to
e161613
Compare
This adds Rails master to CI as an allowed failure. While builds will continue to pass regardless of this run, it makes it easier to keep an eye on if changes need to be made for the upcoming version of Rails, as well as automatically test shims to add compatibility
sgrif
force-pushed
the
sg-run-master-on-ci
branch
from
e161613 to
938361d
Compare
|
I think that #898 might conflict with this. Let's merge this first so we don't have to ask Sean to rebase again and fix a conflict. :) |
|
👍 |
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.
This adds Rails master to CI as an allowed failure. While builds will
continue to pass regardless of this run, it makes it easier to keep an
eye on if changes need to be made for the upcoming version of Rails, as
well as automatically test shims to add compatibility