-
Notifications
You must be signed in to change notification settings - Fork 144
Git dev deployments #7672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Git dev deployments #7672
Conversation
|
||
// merge default branch into edit branch | ||
if force { | ||
// Maybe instead of merge with the "theirs" strategy should we just reset to the default branch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When doing a force merge of default branch to edit branch should we just reset to default branch ?
@@ -167,15 +200,34 @@ func (r *gitRepo) root() string { | |||
|
|||
// commitToEditBranch auto-commits any current changes to the edit branch of the repository. | |||
// This is done to checkpoint progress when the handle is closed. | |||
// If there are conflicts, it should drop any local changes. | |||
// If there are conflicts, it should drop any local changes. Why ?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually there should not be any changes in edit branch that exist on remote but doesn't exist locally but even if there are it should drop those and commit local since this will be triggered on close
or explicit user input
https://linear.app/rilldata/issue/PLAT-94/git-support-for-dev-deployments
TODO: Cleanup git APIs in CLI when UI migrates to API in runtime
Checklist: