This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
fix: make Travis CI usable after the change of GitHub naming scheme for branches #494
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
* bundler 1.12.5 breaks with current version of dependencies (NoMethodError: undefined method `[]' for nil:NilClass) * vagrant-2.2.17 requires ruby version ~> 2.5, < 2.8
glenux
changed the title
|
Hey, sorry for the silence here but this project is looking for maintainers 😅 As per #499, I've added the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi,
This pull request fixes the following issues related to Travis CI :
bundle installoccurring since Github changed their naming scheme for branches (master => main) ;bundle installbecause of outdated dependencies (not matching requirements for vagrant v2.2.17)Successful builds here: