Repository navigation
oxfmt: format the ntfy/gotify builder test - #1680
Merged
Merged
Conversation
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
1 participant
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.
dev's
npm run checkis red right now and its not from any open pr. commit 34f0810 (the test-notify follow-up for #1674) went straight onto dev at 14:46 with one unformatted long line in the ntfy/gotify builder test, and no ci ever ran on that commit. every pr opened after it inherits the failure — #1679 was just the first to trip over it.this is only the formatter's own output on that one line (+4/-1), nothing else. the file's tests pass 14/14 and
oxfmt --check srcis clean with it.merge this one first and #1679's ci can go green once its branch is refreshed onto the new dev.