@withgraphite/graphite-cli 0.22.15 → 1.0.0

package/.CHANGELOG.md

@@ -1,5 +1,71 @@
 # Graphite CLI Changelog
 
+## 1.0.0 2023-09-13
+
+**Renaming and configuration**
+- All commands that fell under `branch`, `stack`, `upstack`, `downstack`, `repo`, and `user` have been renamed to drop the noun. Old command names still work, but will be removed in an upcoming version.
+- The full list of commands is available in `gt --help` or at https://graphite.dev/docs/graphite-cli-v1-command-names.
+- Graphite now supports custom aliasing for any command via `~/.config/graphite/aliases` (or `$XDG_CONFIG_HOME/graphite/aliases`).
+- A preset to copy into this file to keep the old short command names is found at https://graphite.dev/docs/legacy-alias-preset.
+
+- All Graphite configuration now lives in the interactive `gt config` command.
+- Graphite's user-level configuration files are now XDG Base Directory Specification compliant, or stored in `~/.config/graphite` by default.
+
+**gt create**
+- `gt create` is the new command to create a Graphite branch (formerly `branch create`)
+- `gt create` now supports inferring a branch name from the commit editor, which means it is now possible to run it with no arguments.
+- If you have unstaged changes and no staged changes when running `gt create`, you are now asked whether you'd like to stage and commit them as part of the new branch.
+
+**gt modify**
+- `gt modify` is the new command to modify a Graphite branch (formerly `gt commit amend`/`gt commit create`).
+- The default behavior is to amend the current commit on the branch, unless the branch has no commits or `--commit` is passed.
+- When amending a commit, the editor is not opened by default unless `-e`/`--edit` is passed.
+- If you have unstaged changes and no staged changes when running `gt amend`, you are now asked whether you'd like to stage them before running the amend or commit operation.
+- `gt branch edit` has been moved to `gt modify --interactive-rebase`
+
+**gt sync**
+- `gt sync` is the new command to update your trunk branch, clean up merged branches, and restack most branches in your repo.
+- `gt sync` now restacks all branches by default (no longer need `-r`).
+- If any branch has conflicts with its parent branch, instead of launching you into a conflict resolution, `sync` will print out the list of conflicting branches so that you can run `gt restack` on them.
+
+**gt submit**
+- `gt submit` is the new command to push branches to GitHub and create stacked PRs for them.
+- `gt submit` submits the currently checked out branch and its ancestors (dependent branches) by default.
+- `gt ss` is included in the alias file by default as an alias for `gt submit --stack`, which replicates the behavior of the old `gt stack submit`
+- `gt submit` now handles cases where branches in your stack have merged or been updated remotely, as long as there are no rebase conflicts to resolve. This includes both incorporating remote changes and removing merged branches from the stack.
+- `gt submit` now ensures that your branches are restacked instead of failing when they aren't.
+
+**Entirely new commands**
+- `gt pop` to delete the current branch and check out its parent without modifying the working tree. Can't be run if the current branch has children.
+- `gt trunk` to navigate directly to your trunk branch.
+- `gt parent` to print out the raw parent of the branch (for scripting).
+- `gt children` to print out the raw children of the branch, line by line (for scripting).
+- `gt revert` (experimental) to create a branch that reverts a commit in your trunk branch.
+
+**Other changes**
+- Added a new `--stat` flag to `gt info` that prints out a diffstat instead of a full diff. Compatible with either `--diff` or `--patch`.
+- `gt create --insert` now asks which siblings should be moved onto the new branch if there are more than one of them.
+- Performance improvements.
+
+**Bug fixes**
+- Fixed a bug where stray output was printed while completing command names.
+- Fixed an issue where a single optional PR template was interpreted as required PR template.
+- Fixed a bug where branch prefixes could not end with a slash.
+- Fixed a bug where `split --hunk` would not work for branches that added new files.
+- Fixed a bug where the branches created by `split` were all based on the parent of the split branch instead of being stacked correctly.
+- Fixed a bug where the `--patch` flag to `create` and `modify` did not include new files.
+
+**Notes**
+- The `test` command has been temporarily removed due to persistent bugginess, but will be added back when we have time to dedicate to making it work well. For now, one option is to script using the new `gt children` and `gt parent` commands, which should handle most use cases.
+- We are still working on further improvements to `sync` and would love your feedback in this area!
+- We'd also love to ehar about how we can make `revert` work best for you!
+- As of the release of this version, certain parts of the web app and docs may still reference the old command names. We're updating those places as you read this!
+
+## 0.22.16 2023-09-08
+- Added autocomplete support for the renamed commands.
+
+- Fixed a bug in `get` when the PR does not exist locally.
+
 ## 0.22.15 2023-09-07
 - Introduced an environment variable to preview the command rename and custom aliasing system that will be released next week as Graphite CLI v1.  For more details, see https://graphite.dev/docs/graphite-cli-v1-command-names.
 - Introduced a new interactive command `gt config` which covers all user- and repo-level configurations. The `gt user` and `gt repo` top-level commands will be deprecated in an upcoming release.