The Lifecycle of a Pull Request
12 days ago
- #git
- #version-control
- #pull-requests
- Tangled has built a pull request system with three contribution options: paste a patch on the web UI, compare two local branches, or compare across forks.
- Patch generation involves calculating differences between branches, using the 'merge-base' to avoid reverting unintended changes.
- For forks, Tangled uses 'hidden tracking refs' to localize remote branches, enabling comparisons within the same fork.
- Pull requests are stored as atproto records and updated with each patch change.
- Tangled uses a 'round-based' review format, ensuring immutable submissions and clear review tracking.
- Future plans include format-patch support, Gerrit-style refs, Change ID support, and more.
- Tangled now supports jujutsu and has an in-house CI, with sign-up available via email.