feat(forge): migrate forge config, geiger, lint to output channel contract#14973
Merged
Conversation
stevencartavia
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr and
mattsse
as code owners
mablr
requested changes
May 29, 2026
mablr
approved these changes
May 29, 2026
stevencartavia
changed the title
grandizzy
approved these changes
May 30, 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
3 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.
Bundled compliance pass across
forge config,forge geiger,forge lint. Per docs/dev/output-channels.md.forge lint— "nothing to lint" moved to stderr viash_status!.forge config— already compliant (TOML/JSON stay on stdout, no prose). Doc row flipped only.forge geiger— already compliant (delegates to lint, uses warnings). Doc row flipped only.Part of OSS-224