CI: Refer to rack/rack default branch as 'main' #1815
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
This reflects the current default branch of that repository. Issue manifests in CI as: Revision master does not exist in the repository https://github.com/rack/rack.git. Maybe you misspelled it?
olleolleolle
changed the title
|
Ah, I see, there are also Gemfile changes I need to deal with! |
rack/rack default branch is now 'main'
|
Even if things are utterly broken on our side, they're broken for the right reasons, and they break on code not being matched, not due to "we could not download the git repo contents". |
6 tasks
olleolleolle
changed the title
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 PR changes the configured branch name for a GitHub Actions matrix element that runs our test suite with the latest development code of Rack.
Rack has changed the name of the default branch, to
main. This PR now reflects the current default branch of that repository.Issue manifests in CI as:
After this change, we get this, which is more of what we want from a CI job like this (which is exploring the next major version):
Mildly related to #1797