feat: drop error checks and status display - #16
Merged
Merged
Conversation
MingcongBai
force-pushed
the
nuke-error-status
branch
from
January 18, 2026 03:45
da6c67f to
5d4259a
Compare
It seems pointless to display scripting and QA errors on an end-user- facing site, especially when some of the more expensive checks (ELF and file collisions, etc.) were never enabled. Let's keep these errors for maintainers - Autobuild does a good enough job catching them and even GitHub Actions sounds like a better place for these checks.
MingcongBai
force-pushed
the
nuke-error-status
branch
from
January 18, 2026 03:48
5d4259a to
90102cb
Compare
liushuyu
approved these changes
Jan 18, 2026
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.
It seems pointless to display scripting and QA errors on an end-user- facing site, especially when some of the more expensive checks (ELF and file collisions, etc.) were never enabled.
Let's keep these errors for maintainers - Autobuild does a good enough job catching them and even GitHub Actions sounds like a better place for these checks.