Fix recent languages after GitHub API change#25
Open
Conversation
11 tasks
|
I think it would've been cleaner to drop the commits touching the docker file than creating a commit that reverts them (looks like that's the only thing you're doing there, in addition to code formatting). But, if you're squash-merging anyways, I guess the result is the same. |
oddstr13
approved these changes
Mar 21, 2026
oddstr13
left a comment
oddstr13
left a comment
There was a problem hiding this comment.
Update PR title to something along the lines of «Fix recent languages after GitHub API change» and make sure the squash commit contains info to this end, preferably also containing a link to lowlighter#1754 for proper context.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry-pick of lowlighter#1754.