Egit：配置rebase作为master分支的默认pull策略 [英] Egit: configure rebase as default pull strategy for master branch

问题描述

在我们的新项目中，我们有10个存储库，每个存储库都有相互依赖的Eclipse项目。

In our new project we've got 10 repositories, each of which have interdependent Eclipse projects.

我打算建立一个默认工作流，每个开发人员都在工作在主分支上并使用commit-pull-push循环。为了减少提交并获得一个很好的线性历史记录，我更喜欢使用rebase作为标准拉动策略。如果设置了 branch.master.rebase = true ，这可以正常工作。

I plan to establish a default workflow, where each developer is working on the master branch and uses the commit-pull-push cycle. To reduce commits and get a nice linear history I prefer rebase as standard strategy for pull. This works fine, if branch.master.rebase=true is set.

不幸的是，在使用EGit进行克隆之后，必须手动为所有存储库进行设置。我尝试设置 branch.autosetuprebase = always ，但这仅影响手动创建的本地分支，而不影响克隆后的主分支。

Unfortunatelly it has to be set manually for all repositories, after they are cloned with EGit. I tried setting branch.autosetuprebase=always, but this affects manually created local branches only, not the master branch after a clone.

我想自动化初始设置 branch.master.rebase = true 以减少错误并方便起见。有没有办法做到这一点？最好在Eclipse / Egit内部，但也欢迎其他想法。

I would like to automatize the initial setting of branch.master.rebase=true to reduce errors and for convenience. Is there a way to do it? Preferably inside of Eclipse/Egit, but other ideas are welcome, too.

推荐答案

[branch]
    autosetuprebase=always

$ b $ .gitconfig

这篇关于Egit：配置rebase作为master分支的默认pull策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！