You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2022. It is now read-only.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: