-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Can we provide 2 queries per repo? #578
Comments
xref #344 |
A little bit digging around.
Another option is to embed the URL in 'desc' markdown - at least it seems that it is treated like markdown - here, with showdown |
Perhaps this could come in the form of an optional key for linking to a CONTRIBUTING file (or a section within that, if there's a UFG section)? That said, I'm not opposed to supporting multiple labels, too/instead (please discuss that in #344). Or links within descriptions, for that matter. |
So links within description are not allowed at this moment? Your code seems to treat them as mark down, so I would assume it should just work ... BTW: I was about to try it out, but got stopped by missing pre-req 'bundle', have to hunt it down somewhere ... |
I wouldn't say links aren't allowed, I just don't know if anyone has tried. They're fine with me... For bundle, you need to |
|
@karelz there's a Dockerfile at the root which should be setup for this. |
Would be nice to promote a query with 'simple' issues for a repo (we do not have too many yet marked with 'simple', but it's coming ...).
However, we don't want to make it the main query from your site http://up-for-grabs.net.
Maybe even better option: Optionally provide a link to "up-for-grabs issue guide" per repo, where we could have few links - simple issues for beginners, up-for-grabs which are NOT API proposals (proposing CoreFX APIs actually requires special skills and patience), wishlist we would really like, but won't get to it and issues for upcoming release (i.e. most impactful)
Does it sound like a reasonable request or is it too complex?
Happy to chip in if you point me in the right direction ... (where yml schema is enforced and how is it translated in db/html/JavaScript/other magic)
FYI: Details discussed here: https://github.com/dotnet/corefx/issues/17533#issuecomment-289323239
The text was updated successfully, but these errors were encountered: