Replies: 2 comments
|
Hey! The changes I made are super minor. It should be easy to keep it in sync because of that, with agents getting the latest from upstream and then reapplying the changes we need for the app on top of those I'm going to reduce them as much as possible with time by doing them on app side where possible. I think it's just three or four changes that I need to apply, and they don't need to be upstream. I'm not planning to really fork ghostly in any big way. It's just going to be a super light fork, and keeping it in sync should be super easy. |
0 replies
|
Thank you for your response! The small change-surface is reassuring, and it should be a small lift to pull in the upstream changes from ghostty each release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Howdy!
Ghostex has a sleek UI and I'm excited to learn to use it! However, one aspect gives me pause before committing to learning a new tool. How does this project intend to remain in sync with Ghostty's upstream revisions? And do the authors intend to contribute changes upstream when it makes sense?
Thanks!
All reactions