This message was deleted.
# feature-requests
s
This message was deleted.
1
s
one issue we encountered was that initially the feature branch is empty, so graphite will keep prompting you to delete it as it considers it fully merged
another is that you cannot merge branches to the feature branch using graphite dashboard. you can only queue the entire stack, including the feature branch. so no automatic restacking
and this one i'm not 100% sure of, but i think another issue was that once you merge a child to the feature branch (using github), graphite wasn't recognising this properly, so if you pulled the data from repo, you might encounter merge conflicts