[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[savannah-help-public] [sr #109017] Git branches other than master shoul
From: |
Juan Pedro Bolivar Puente |
Subject: |
[savannah-help-public] [sr #109017] Git branches other than master should allow non-fast-forward commits |
Date: |
Wed, 20 Apr 2016 13:51:30 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
URL:
<http://savannah.gnu.org/support/?109017>
Summary: Git branches other than master should allow
non-fast-forward commits
Project: Savannah Administration
Submitted by: raskolnikov
Submitted on: mié 20 abr 2016 13:51:29 GMT
Category: Source code repositories - developer access
Priority: 5 - Normal
Severity: 3 - Normal
Status: None
Assigned to: None
Originator Email: address@hidden
Operating System: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Hi!
Git repositories in Savannah have blocked `push --force` after rebase. I do
very much understand the rationale for this being the case for the `master`
branch, but otherwise this is unnecessary hassle. These are branches that are
for development of features, and being able to cleanup the history makes code
review, "git blame" and "git bisect" much easier.
I did read the rationale here: https://savannah.gnu.org/maintenance/UsingGit/
I find that rationale unconvincing, since one can still remove the branch with
`git push origin :mybranch`.
In fact, that is my workaround: delete the branch and push again. And an
unnecessary hassle, that adds more risk.
Thanks for taking this suggestion into consideration.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?109017>
_______________________________________________
Mensaje enviado vía/por Savannah
http://savannah.gnu.org/
- [savannah-help-public] [sr #109017] Git branches other than master should allow non-fast-forward commits,
Juan Pedro Bolivar Puente <=