@withgraphite/graphite-cli 1.0.7 → 1.0.9

package/.CHANGELOG.md

@@ -1,6 +1,23 @@
 # Graphite CLI Changelog
 
+# 1.0.9 2023-10-23
+
+- Improved how PR descriptions are persisted across aborted `submit` runs.
+- Modified version prompting so users are only asked to upgrade their CLIs once per day.
+
+- Fixed a bug in remote changes detection.
+
+# 1.0.8 2023-10-16
+
+- Added a `--update` option for `create` and `modify` that stages changes to all already-tracked files.
+- Added support for `gt get <pr-number>`.
+- Added a `--comment` flag to `submit` which will add a comment with the provided text to the submitted PR.
+- Added additional debugging information to the output file of the `--debug` flag.
+
+- Fixed a bug where the incorrect version number was displayed after running `gt get` for a remote branch.
+
 # 1.0.7 2023-10-04
+
 - Added `gt aliases --legacy` command to automatically add all of the old shortcuts to your aliases configuration.
 - Added ability to navigate through prompts using ctrl+n and ctrl+p.
 - Updated `submit` description behavior to include commit messages if no default template exists.
@@ -11,15 +28,18 @@
 - Fixed incorrect `restack` deprecation warning.
 
 # 1.0.6 2023-09-29
+
 - Updated the default behavior on `gt submit` to not restack branches.
 - Added an optional `--restack` flag to `gt submit`.
 - Always prompt on `gt submit` if the branch will have conflicts with main.
 
 ## 1.0.5 2023-09-18
+
 - Fixed a stray line of output in `gt create`.
 - Fixed an issue where syncing PR data from remote could set the wrong parent.
 
 ## 1.0.4 2023-09-18
+
 - Updated `--help` output to be more consistent and more helpful.
 - Added a new command `gt aliases` to open up the alias file in your editor.
 - Now removes `~/.graphite_user_config` once your configuration has been moved to the new location to reduce confusion.
@@ -48,11 +68,13 @@
 - Fixed the error messge when running a deprecated command to print the correct alias file location.
 
 ## 1.0.1 2023-09-14
+
 - Fixed a bug where `gt submit --stack` did not work from the trunk branch.
 
 ## 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`).
@@ -62,11 +84,13 @@
 - 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.
@@ -74,11 +98,13 @@
 - `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`
@@ -86,6 +112,7 @@
 - `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).
@@ -93,11 +120,13 @@
 - `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.
@@ -106,18 +135,21 @@
 - 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 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.
 
 - `checkout` now prompts to `sync` when the branch's PR has been merged.
@@ -128,6 +160,7 @@
 - Fixed a bug where an `git range-diff` failure could block submit.
 
 ## 0.22.14 2023-09-06
+
 - Fixed a bug where users with a Yubikey-protected SSH key were unable to `sync`.
 - Fixed a bug where an uncaught IPC exception would appear after running a command.
 
@@ -154,10 +187,9 @@
 - Fixed an issue where `downstack get` failed with an incorrect error message.
 - Fixed some issues with incosistent failures in `get`
 
-
 - Added an experimental `.graphite_aliases` file (see below)
 
-We are currently in the process of renaming all Graphite commands. This version is the first one with the full set of renamed commands implemented. If you'd like to try out this new command surface, you can add "export GT_RENAME=1" to your shell configuration file (e.g. ~/.zshrc) to be warned when you run a renamed command and what the new name is. It may be unstable and is primarily meant for employee testing purposes until further notice. There is no overlap between the old set of commands and the new set.  For more information, see https://www.notion.so/withgraphite/Proposal-for-Graphite-CLI-changes-400d068c7c8546fcbc90b5573e6f27e9?pvs=4.
+We are currently in the process of renaming all Graphite commands. This version is the first one with the full set of renamed commands implemented. If you'd like to try out this new command surface, you can add "export GT_RENAME=1" to your shell configuration file (e.g. ~/.zshrc) to be warned when you run a renamed command and what the new name is. It may be unstable and is primarily meant for employee testing purposes until further notice. There is no overlap between the old set of commands and the new set. For more information, see https://www.notion.so/withgraphite/Proposal-for-Graphite-CLI-changes-400d068c7c8546fcbc90b5573e6f27e9?pvs=4.
 
 The cool part is that turning this configuration on allows you to set custom aliases via the `~/.graphite_aliases` file, which we know some of you have been asking us about for quite a while!
 
@@ -193,7 +225,7 @@ The cool part is that turning this configuration on allows you to set custom ali
 - `downstack get` now automatically pulls in changes from GitHub if the local state of the branch matches a submitted version of the branch's open pull request.
 - `submit` commands now suggest running `downstack get` when the above situation is detected.
 
-- YubiKey prompting for SSH is now moved behind a config, in order to address some bugs that passing through the YubiKey prompt introduced.  If you are using a YubiKey to authenticate with GitHub, you can enable this config with `gt user yubikey --enable`.
+- YubiKey prompting for SSH is now moved behind a config, in order to address some bugs that passing through the YubiKey prompt introduced. If you are using a YubiKey to authenticate with GitHub, you can enable this config with `gt user yubikey --enable`.
 
 - Added a global `--cwd` flag to run any Graphite command in a directory other than the one it is initiated from.