Dexter Miguel12/05/2023, 2:22 AM
is very unreliable when it comes to syncing the state of a local branch to remote. it used to work just fine and now i’m constantly running into issues. often branches that get merged don’t get correctly closed. additionally branches that get merged into other branches throw
into a state of chaos whereas before it knew it needed to fold the branch. anyhow just in general not enjoying this update whatsoever
Ben Jaffe12/05/2023, 2:29 AM
Veith Röthlingshöfer12/05/2023, 11:52 AM
, and fix all remaining files manually, then do
and then "continue works again". Very weird behavior.
gt add -A
Noé RUBINSTEIN12/05/2023, 2:18 PM
is kind of wonky? (I just tried this option out of curiosity, this is not an important bug report)
Cal Courtney12/05/2023, 3:46 PM
Graham Jans12/05/2023, 6:25 PM
Cal Courtney12/05/2023, 6:49 PM
Zhiwei Chong12/06/2023, 1:44 AM
I have been sticking to the legacy aliases and using
There have been remote changes to my_awesome_branch. Check out the branch and run `gt get`, then try submitting again. To overwrite remote changes, use the use the --force option of gt submit.
though- could that be why?
Valentin Hervieu12/06/2023, 11:06 AM
, it says:
Then, if I run
There is no tracking information for the current branch. Please specify which branch you want to merge with. See git-pull(1) for details. git pull <remote> <branch> If you wish to set tracking information for this branch you can do so with: git branch --set-upstream-to=origin/<branch> my-branch-name
Am I doing anything wrong?
my-branch-name is already tracked.
Veith Röthlingshöfer12/06/2023, 12:46 PM
Ben Jaffe12/06/2023, 3:23 PM
in a comment box, it doesn't work if I don't have a space preceding. This happens often when I add a comment, and then edit to tag someone, or if I try to
in the middle of a sentence. It's not terrible, but I run up against this friction maybe 5 times a day.
Tyler Laprade12/06/2023, 7:13 PM
Greg12/06/2023, 7:20 PM
Dave Caruso12/06/2023, 11:32 PM
Ben Jaffe12/07/2023, 1:16 PM
Tao Bojlén12/07/2023, 1:34 PM
Ben Jaffe12/07/2023, 2:53 PM
Yash Shah12/07/2023, 3:09 PM
However, when I go on the site and create a token, it vanishes when I refresh the page, and using the new token on the CLI still throws the same error
ERROR: Your Graphite auth token is invalid/expired. Please obtain a new auth token by visiting <https://app.graphite.dev/activate>.
Dexter Miguel12/07/2023, 4:50 PM
Martin Ek12/07/2023, 5:46 PM
Laurent S12/07/2023, 7:24 PM
Ella Rohm-Ensing12/07/2023, 8:38 PM
seems to swallow the
logging of pre-push hooks. Specifically this:
Because it's a longer running hook, it makes it look like graphite is hanging on
Running formatting (~30s).......................
and I don't want my team's new graphite users to get stuck on this 🙂 If the hook succeeds, we don't get any logs when doing it through graphite, though we get the info with raw git because we have the hook with
:incoming_envelope: Pushing to remote and creating/updating PRs...
If the hook fails, we get the entire logs of the hook in red (harder to grok than normal) because it's error output from
ERROR: Command failed with error exit code 1:
Gustavo Nunes Goretkin12/07/2023, 9:22 PM
) generate any stdout output except for
flag does not help. There is no stdout output telling us where the log file is. Based on other machines, it should be in
, but there is no
dir there. We tried Graphite version
, and this is on node version
Tyler Laprade12/07/2023, 10:18 PM
Dirk Meister12/08/2023, 6:46 PM
Jackie Luo12/08/2023, 7:53 PM
Ivan Vanderbyl12/08/2023, 10:59 PM
// Code generated by ent, DO NOT EDIT. // Code generated by protoc-gen-connect-go. DO NOT EDIT.
Shuo Yang12/08/2023, 11:11 PM
Lee G12/09/2023, 8:11 PM
, or any graphite commands don't work with the exception of