bitbucket剥离了git修订版 [英] bitbucket stripped git revisions

问题描述

 剥离了6f9de58aa748 from projektA $ b $在推送到bitbucket后，我的同事提交被删除，并在bitbucket新闻源中显示一条消息b 4小时前
被剥离54dae89de600 from projektA 
 4小时前
剥离e04022989a9d from projektA 
 ... 
  

我如何解救提交？
Git真的是一个允许删除提交的版本控制系统吗？
这是由于--force？

解决方案

如何拯救提交？

不幸的是，您无法在您的网站上完成这些提交（详情）。您需要联系BB服务团队，因为只有他们可以恢复这些提交。

Git真的是一个允许删除提交的版本控制系统吗？

如此配置它。您必须将> receive.denyNonFastForwards 设置为 true 以在服务器上的存储库中禁用此行为（这是默认当使用 - 共享选项运行 git init 时，其他情况下为false。）

是否由于--force？

如果你的新分支头部抛出其他的提交，并且 receive.denyNonFastForwards， git push 上的强制参数会使服务器端git禁用安全检查为假。

After pushing to bitbucket my collegues commits are deleted and a message appears on bitbucket newsfeed

stripped 6f9de58aa748 from projektA
4 hours ago
stripped 54dae89de600 from projektA
4 hours ago
stripped e04022989a9d from projektA
...

How can I rescue the commits? Is Git really a versioning system that allows to delete commits? Is this due to --force ?

解决方案

How can I rescue the commits?

Unfortunately there is nothing you can do on your site to get these commits back (details). You need to contact the BB service team since only they can restore these commits.

Is Git really a versioning system that allows to delete commits?

When you configure it so. You have to set receive.denyNonFastForwards to true to disable this behavior in the repository on the server (which is the default when git init was run with the --shared option, but is false otherwise).

Is this due to --force ?

Yes, using the force parameter on git push does make the server side git to disable the safety check if your new branch head throws away other commits, and receive.denyNonFastForwards is false.

这篇关于bitbucket剥离了git修订版的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！