Bugzilla – Full Text Bug Listing
| Summary: | Unable to push to a new remote branch | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Maciej Bendkowski <maciej.bendkowski> | ||||
| Component: | Git | Assignee: | Silenio Quarti <Silenio_Quarti> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | gheorghe, ken_walker, Mike_Wilson, Silenio_Quarti | ||||
| Version: | unspecified | Flags: | gheorghe:
review+
|
||||
| Target Milestone: | 6.0 RC3 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
When one ignores the error messages it's still possible to push a remote branch, however the incoming/outgoing commits are not displayed and the remote tracking branch is not updated. remoteBranch.CommitLocation @ gitCommitList.js around line 93 seems to be undefined after changing the remote branch. |
Created attachment 244549 [details] JavaScript console log Steps to reproduce: 1. Navigate to the git repository page. 2. Click the "Choose another branch" button. 3. Select "origin" and type a new branch name, e.g. "test". Click OK. You should get an error: "No ref or commit found: origin/test". Investigating the JavaScript console, it turns out that the issue is caused by a wrong crafted URL containing the "undefined" literal (see attachment).