Repository navigation
fix: give the remaining app config settings an empty-string default #645
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 file contains hidden or 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 file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few other releases 4.2.1 4.2.2 4.3.2 that have gone missing from this section.
Maybe fix that in a follow-up PR (not directly related to this)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, and done as a follow-up: #646.
It turned out to be a bit more than missing entries. Five headings had no definition at all —
4.2.1,4.2.2,4.2.3,4.3.0,4.3.1(there is no 4.3.2 yet) — and on top of that two of theexisting definitions pointed at tags that were never created, so they were live 404s:
[4.0.0]→compare/v3.0.1...v4.0.0—v3.0.1was only ever tagged-beta.1/-rc.1[3.0.1]→ same missing tag, and an orphan: there is no## [3.0.1]section[2.4.0]→compare/v2.2.0...v2.4.0—v2.4.0is the oldest tag in the repo#646 fetches every link in the block afterwards: all 15 return 200, and every section heading has
exactly one definition.
One thing worth knowing: #646 touches this same contiguous block, so the two conflict by
construction. Merging this PR first and letting me rebase #646 is the easy order.