Skip to content
This repository has been archived by the owner on Sep 20, 2022. It is now read-only.

When issue tracker is not found, remote should be used #80

Open
JakeGinnivan opened this issue Apr 12, 2015 · 2 comments
Open

When issue tracker is not found, remote should be used #80

JakeGinnivan opened this issue Apr 12, 2015 · 2 comments

Comments

@JakeGinnivan
Copy link
Contributor

This feature no longer works. If using Github for source and issues it used to use the remote defined in the repo to infer the issue tracker.

Also worked for Bitbucket and should work for TFS when that is done

@GeertvanHorrik
Copy link
Contributor

I know I probably broke a few things with the transition to the new context. I will look into it when I can.

@JakeGinnivan
Copy link
Contributor Author

I just threw then up to track/discuss. Don't stress, I've not had time to look into it properly

Sent from my Windows Phone


From: Geert van Horrikmailto:[email protected]
Sent: ‎18/‎04/‎2015 09:50
To: GitTools/GitReleaseNotesmailto:[email protected]
Cc: Jake Ginnivanmailto:[email protected]
Subject: Re: [GitReleaseNotes] When issue tracker is not found, remote should be used (#80)

I know I probably broke a few things with the transition to the new context. I will look into it when I can.


Reply to this email directly or view it on GitHubhttps://github.com//issues/80#issuecomment-94141038.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants