Loving graphite so far, definitely seems to speed ...
# how-do-i
c
Loving graphite so far, definitely seems to speed up our review process. But wondering how to work with efficiently with a feature / epic branch. Right now, I create a branch for a feature, add it as a trunk via repository settings, and start stacking from the feature branch. All going well, except, a co-worker did a few modifications on a stacked PR, and submitted them. This changed the base of the branch to our main trunk branch (develop), and not the feature branch. I think the local repository config I had setup for trunk branches did not sync to his graphite config. Is this a limitation of graphite, or something wrong in our workflow?
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 Cees — I think this may be a Graphite limitation limitation. The trunk branch that a user's branches will be based from is set per repo in the user's individual
gt config
. This is a local setting that does not "sync" to another user's config automatically. More info about setting and using multiple trunk branches in our docs here. As you're collaborating on a stack, you should also check out the new "frozen" branches feature introduced in
1.7.0
.