Graphite Community

Graphite is introducing a new CLI Beta process! Instructions & notifications for when new beta versions are available will be posted in this channel.

Is there a special incantation to get the beta release?

I believe that is coming later this week :slightly_smiling_face:

CLI version 1.0.7 is available for beta!

To install, run `npm install -g @withgraphite/graphite-cli@beta`. We are working on installation instructions for brew as well.

Release notes:
- 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.
- Updated how we detect if there are remote changes to a PR that need to be resolved.

- Fixed a bug where local state could become corrupt after switching trunk branch.
- Fixed a bug where we were syncing information for untracked branches.
- Fixed incorrect `restack` deprecation warning.

yessss to the commit messages in description!

If we delete the description, will it populate? In my case, I have a template (to remind people to describe their changes) but I still want the commit message behavior if possible

you can get both the commit messages + template via `gt config` settings

this just makes the default a little saner

image.png

This should be putting both the template and the commit messages in the description right? Right now it's only using the template.

well have instructions for brew by tomorrow if not today!

CLI beta is also available for brew:
```brew install withgraphite/tap/graphite-beta```


I've installed the legacy aliases and my life is _soooooo_ much better. :slightly_smiling_face:

set the channel description: npm install -g @withgraphite/graphite-cli@beta

I did get nagged about using `gt be`:
```; gt be
Successfully rebased and updated refs/heads/amonshiz/prdi-1831/include-macos-13.6-snapshots.
WARNING: This command has been renamed and will be fully removed soon. Please use gt modify --interactive-rebase instead.
You can now use gt aliases to configure your own command aliases.
Try gt aliases --legacy to automatically add all of the old shortcuts to your aliases configuration.```
Do I need to reload my shell after adding those aliases?

Opening a new shell didn't change the fact the "Warning" was shown :disappointed:

But I'm still thankful that these aliases are so easy to add now

set the channel description: npm install -g @withgraphite/graphite-cli@beta
brew install withgraphite/tap/graphite-beta

CLI version `1.0.8` is available for beta!
Installation instructions available here: <https://graphite.dev/docs/beta-cli>

Release notes:
- Added an `--update` option for `create` and `modify` that stages changes to all already-tracked files.
- Added support for `gt get &lt;pr-number&gt;`.
- 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.

&gt; Added a `--comment` flag to `submit` which will add a comment with the provided text to the submitted PR.
:gopher_party:

Is the yellow warning text still displaying even when an alias is in place to mimic an old command?

<@U02RREE9GKH> Unfortunately still getting the deprecation message for my `cc` alias:
```amonshiz@amonshiz-tbc-mbp2 ~/Developer/infra (amonshiz/prdi-1853/try-ssh-retries)
; gt cc -m 'Add SSH retries to try and silence spurious failures'
[amonshiz/prdi-1853/try-ssh-retries 63c5d05] Add SSH retries to try and silence spurious failures
 1 file changed, 4 insertions(+)
WARNING: This command has been renamed and will be fully removed soon. Please use gt modify -c instead.
You can now use gt aliases to configure your own command aliases.
Try gt aliases --legacy to automatically add all of the old shortcuts to your aliases configuration.

amonshiz@amonshiz-tbc-mbp2 ~/Developer/infra (amonshiz/prdi-1853/try-ssh-retries)
; gt --version
1.0.9

amonshiz@amonshiz-tbc-mbp2 ~/Developer/infra (amonshiz/prdi-1853/try-ssh-retries) [1]
; cat ~/.config/graphite/aliases | rg cc
cc modify --commit```


Double release week - CLI version `1.0.9` is available for beta.
Release notes:
Changelog:
- 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.

CLI version `1.0.10` is available for beta.

Release notes:
- Updated the `gt submit --draft` flag to only no longer convert already published PRs back to drafts.
- Added support for team reviewers. Team reviewers can either be specified using `gt submit --team-reviewers slug` or through `gt submit --reviewers org/slug`.

- Added output to `log short` when a branch needs to be fetched from remote (using `gt get`).
- Added output after `gt checkout` specifying whether a branch needs to be submitted, fetched, or restacked.

- Removed a reference to legacy command names.

&gt; - Removed a reference to legacy command names.
Does that mean I won't get nagged for having configured aliases that mimic the old commands? :smile:

No, but that’s coming in the next release!

CLI version `1.0.11` is available for beta.
Release notes:
• Fixed bug where aliases were not respected.
• Added retry when fetching branch from remote fails.


<@U02PSKGK4TS> This should be the alias change you were waiting for!

<@U05D5ADT4K1> please pass my thanks along to whomever removed the nags cause my life is _sooooo_ much better now :smile: