This message was deleted.

cc @David Bradford for merge-related requests

CC @Xiulung Choy @merrill I believe they will have more context on the history/future here.

Hey @Mohammad Abed sorry for the delayed response. So today, Graphite uses whatever default branch you have set in GitHub to determine where stacks “should” be merging into, and since the repo’s default branch is set to

main

Graphite wanted to warn you that were able to merge into a branch that isn’t the default branch. Perhaps the messaging is too forward and we should probably change this to a warning that reads

This stack is merging into Feature_Branch and not the repo

In the long run we want to update the web app and the CLI to be more aligned in regards to the base of the stack and make it easier to set and change. Do you regularly switch between trying to merge into a feature branch and into main? Do you need to merge into the feature branch first before handing off to QA? Do you have a perspective on what the ideal workflow would be for you here?