what's the rationale behind freezing diffs that i ...
# how-do-i
l
what's the rationale behind freezing diffs that i
gt get
? i'm bringing them into my environment so i can edit and collaborate on this stack. should i be doing something else?
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
Hey Luke, the intention is to prevent accidentally making edits a collaborators branch versus adding to the stack. Quick read on it here and longer read here
l
it's not obvious how we can collaborate on a stack if diffs are frozen because they cannot be rebased
p
will share this feedback
l
i guess the owner of the freezed diffs rebase their own? not sure
i guess it could make sense if the web dashboard made it easy to combine diffs. for example co-worker's diff has red ci. i come in to make it green. i can't really do that below their pr. i can do it above, but his frozen diff is still red
p
in that scenario, you could also unfreeze and modify. folding in the UI is coming soon.
its not meant to entirely block editing collaborators work, its meant to block accidentally do so.
t
Graphite is working around people naively running
gt get
and then accidentally rebasing their coworker's branch. Since you're an expert and know what you're doing, just retrain yourself to use
gt get --unfrozen
(
gt get -U
) any time you run
gt get
and you'll get the behavior you expect.