Skip to content

docs: preserve fork maintenance workflow #93

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tarik02 merged 1 commit into from
Jul 29, 2026
Merged

docs: preserve fork maintenance workflow #93

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions FORK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@

This repository is a fork of `pingdotgg/t3code`. Keep this file focused on fork behavior that intentionally differs from upstream.

## Maintenance Workflow

- Update this file in the same change whenever fork-only behavior changes.
- Keep workflow-only fork changes narrow and prefer job-level disables over broad refactors.
- Do not commit package version bumps solely to represent fork releases.
- Re-check Electron updater channel behavior when changing version strings, release metadata, or desktop packaging.
- Prepare fork PR branches from `origin/main` and target `tarik02/t3code:main`.
- If a fork PR branch includes unintended upstream history, rebuild it from `origin/main` and replay only the intended diff.

## Changes

### Maintenance
Expand Down
Loading