Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@aochagavia
Copy link
Contributor

It points now to the issues on the GitHub repository

@khellang
Copy link
Member

Isn't "https://github.com/dotnet/roslyn/labels/Up%20for%20Grabs" more correct? Just sent a PR to up-for-grabs.net as well 😄

@aochagavia
Copy link
Contributor Author

I think that one would also show closed issues. Wouldn't it?

@adamralph
Copy link
Contributor

IIRC, last time I checked, 'up-for-grabs' was more common.
On 28 Jan 2015 11:34, "Kristian Hellang" [email protected] wrote:

Isn't "https://github.com/dotnet/roslyn/labels/Up%20for%20Grabs" more
correct? Just sent a PR
up-for-grabs/up-for-grabs.net#150 to up-for-grabs.net
as well [image: 😄]


Reply to this email directly or view it on GitHub
#103 (comment).

@khellang
Copy link
Member

I think that one would also show closed issues. Wouldn't it?

Nope, if you check the link, it'll search for is:open label:"Up for Grabs" 😄

EDIT: It will include PRs, though. Not sure that's an issue.

@khellang
Copy link
Member

IIRC, last time I checked, 'up-for-grabs' was more common.

Not sure that'll work, since the label itself is "Up for Grabs".

@adamralph
Copy link
Contributor

Yep, my comment was out of context. I should probably have a look at the PR
rather than blindly replying by email 😃. It was a comment about the
name of the label itself.
On 28 Jan 2015 11:41, "Kristian Hellang" [email protected] wrote:

IIRC, last time I checked, 'up-for-grabs' was more common.

Not sure that'll work, since the label itself is "Up for Grabs".


Reply to this email directly or view it on GitHub
#103 (comment).

It points now to the issues on the GitHub repository
@aochagavia
Copy link
Contributor Author

@khellang I have updated the commit with your link 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants