I documented how glab stack sync behaves on fork-based workflows after the underlying bug fix shipped.
The original fix prevented broken merge requests, but users still needed clear guidance on why fork users are prompted to choose a repository and what to pick.
I updated the CLI docs to explain:
- when the prompt appears in fork flows,
- how to choose the correct remote safely,
- and how this avoids syncing to the wrong project.
This was my first merged OSS contribution and went through normal maintainer review before merge.
Links: MR !1723 • Issue #7660 • Related fix !1687