docs(ghostty): add libghostty fork maintenance rules - #76
Merged
Merged
Conversation
nek0der
force-pushed
the
docs/libghostty-fork
branch
from
September 15, 2026 15:26
3aadabe to
07b1f0e
Compare
nek0der
enabled auto-merge (squash)
September 15, 2026 15:34
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
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.
Summary
Adds
docs/libghostty-fork.md, a standing document for how we maintain thelibghostty fork: why it exists, what a patch must carry, how we rebase, and
how we retire one. Brings the existing fork patch up to those rules by
recording its class and retirement condition in its commit message. No
tracked source changes — the submodule bump rewrites a commit message and
leaves the tree byte-identical.
Related issue
Skip.
How verified
git check-ignore—docs/libghostty-fork.mdis not ignored; local notesdirectly under
docs/still are.the expected values: one patch carried, 133 commits behind upstream.
git rev-parse— the submodule's new tip has the same tree as the old one,so no build output can change.
pin/2026-09-06tag, pushed to the fork.make lint— Rust and Swift checks pass with zero violations.make test— Rust, XCTest, and Swift Testing suites all pass.Screenshots / video
Skip.
Checklist
make lintclean locallymake testpassesmake review-corepasses (its own CI job;make testdoes not cover it)Localizable.xcstringswith both en and ja