Bugzilla – Full Text Bug Listing
| Summary: | [Papyrus] [Moka] There is no possibility to push a new master branch | ||
|---|---|---|---|
| Product: | Community | Reporter: | Quentin Le Menez <quentin.lemenez> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | jeremie.tatibouet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Quentin Le Menez
Just an update as to let you know that going through Jeremie it went as planned and the new master has been created, but I would still like to have the rights on this (and possibly on all other Papyrus repositories) repository. Thanks, Quentin The issue with your push is that you can't push commits that belong to other people. -M. ha ! you mean to say that I could not push the master branch because there were commits on it that did not belong to me ? Is it because I am not considered a committer on this project ? that would be strange as I am one on the Papyrus one, or maybe there are permissions distinct to all the git repository created under the Papyrus project ? Quentin (In reply to Quentin Le Menez from comment #3) > you mean to say that I could not push the master branch because there were > commits on it that did not belong to me ? > Is it because I am not considered a committer on this project ? that would > be strange as I am one on the Papyrus one, or maybe there are permissions > distinct to all the git repository created under the Papyrus project ? > The Eclipse IP check plugin checks that all commits being submitted belong to the same person, regardless of branch. Committer status doesn't provide an 'override' of this requirement. Permissions should be the same across all of a given projects repos. If you believe that isn't the case let me know which repos you think should be checked. -M. Hi, To resume what was done on the repo org.eclipse.papyrus-moka.git : I deleted the moka-master branch (which resulted in the deletion of the master branch for some reason. the former was based on the later), than proceeded to push the renamed local branch (moka-master -> master) to the remote. This was denied with the associated message in comment#1. I looked at the Moka repository and there were contributions from multiple people (mostly jeremie and sebatien). What was puzzling me was that Jeremie could push the new "master" branch (containing all the commits) and not me. Could it be that, because Sebastien was not a committer and Jeremie merged them for him that those commits were considered to be Jeremie's ? Thanks and sorry for the hassle. Quentin (In reply to Quentin Le Menez from comment #5) >. Could it be that, because Sebastien > was not a committer and Jeremie merged them for him that those commits were > considered to be Jeremie's ? I would expect that to fail in the same way as your error, but I'm not a Git wizard. Looking at the permissions I suspect Jeremie was leveraging 'force-push' to re-write the history. We don't grant force push by default so I've removed that permission. -M. Ok thanks it must have ben that then. I'll close this as the issue has virually been resolved. |