Bug 472410 - Saving github.com tasks repository properties adds "/pulls" suffix to Server field value
Summary: Saving github.com tasks repository properties adds "/pulls" suffix to Server ...
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: GitHub (show other bugs)
Version: 4.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-10 21:08 EDT by Denis Golovin CLA
Modified: 2016-05-03 11:34 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Denis Golovin CLA 2015-07-10 21:08:56 EDT 
This leads to "Open with Web Browser" opening wrong url for the pull request on github.com

Steps to replicate are:
1. Create github.com tasks repository with 
   Serve: https://github.com/jbosstools/jbosstools-fremarker
   Name: Freemarker PRs
   Anonymous: checked
2. Open Task Repositories View 
3. Request Properties for created repository (1) from context menu
4. Re-size dialog to see properties (see Bug 472409 for details)
5. Press Finish
6. Open Properties again and check Server field value is https://github.com/jbosstools/jbosstools-fremarker/pulls
7. Press Finish
8. Open Properties dialog for repository (1) and check Server value is https://github.com/jbosstools/jbosstools-fremarker/pulls/pulls
Comment 1 Patrick-Jeffrey Pollo Guilbert CLA 2016-05-03 11:34:18 EDT 
(In reply to Denis Golovin from comment #0)
> This leads to "Open with Web Browser" opening wrong url for the pull request
> on github.com
> 
> Steps to replicate are:
> 1. Create github.com tasks repository with 
>    Serve: https://github.com/jbosstools/jbosstools-fremarker
>    Name: Freemarker PRs
>    Anonymous: checked
> 2. Open Task Repositories View 

Just a heads up, the github URL ends up 404'ing. But trying with another test repo of mine, it seems to work and I can't reproduce the bug you've listed. Has it been fixed?