First off, thank you for building such a fast and pleasant git client, it's genuinely made my day-to-day git workflow better, and I appreciate the care that clearly goes into it.
I wanted to flag a new GitHub feature and gauge your interest in supporting it. GitHub recently rolled out stacked pull requests (currently in public preview), managed through a new gh stack CLI extension. It lets you break a large change into a chain of smaller, dependent PRs, each one targeting the branch below it, so reviewers can review and merge each layer independently instead of facing one giant diff. Docs here if useful: https://docs.github.com/en/pull-requests/get-started/stacked-prs-quickstart
That said, I completely understand if this isn't a great fit for Fork's roadmap. This is a GitHub-specific feature, and I know Fork intentionally supports multiple providers (GitHub, GitLab, Bitbucket, Azure DevOps), building deep support for something so tied to one vendor's workflow could mean disproportionate effort for a feature that only benefits a slice of your users, or could nudge Fork toward GitHub-specific lock-in in a way that cuts against the tool's philosophy. If that's the calculus, I get it, and I'll understand if it doesn't make the cut.
Just wanted to put it on your radar in case it's something you'd already been considering. Thanks again for all the work you put into Fork!
First off, thank you for building such a fast and pleasant git client, it's genuinely made my day-to-day git workflow better, and I appreciate the care that clearly goes into it.
I wanted to flag a new GitHub feature and gauge your interest in supporting it. GitHub recently rolled out stacked pull requests (currently in public preview), managed through a new gh stack CLI extension. It lets you break a large change into a chain of smaller, dependent PRs, each one targeting the branch below it, so reviewers can review and merge each layer independently instead of facing one giant diff. Docs here if useful: https://docs.github.com/en/pull-requests/get-started/stacked-prs-quickstart
That said, I completely understand if this isn't a great fit for Fork's roadmap. This is a GitHub-specific feature, and I know Fork intentionally supports multiple providers (GitHub, GitLab, Bitbucket, Azure DevOps), building deep support for something so tied to one vendor's workflow could mean disproportionate effort for a feature that only benefits a slice of your users, or could nudge Fork toward GitHub-specific lock-in in a way that cuts against the tool's philosophy. If that's the calculus, I get it, and I'll understand if it doesn't make the cut.
Just wanted to put it on your radar in case it's something you'd already been considering. Thanks again for all the work you put into Fork!