How to add repositories?
bodokaiser opened this issue · 12 comments
just add them to https://github.com/component/component/wiki/Components, they'll be added to the website by a periodic grabber.
Thank you will do this!
PS: Hattest damals recht component besiegt jede fertig MVC Lösung. Zum Glück habe ich das jetzt auch einsehen ;)
Am 18.07.2013 um 10:12 schrieb Julian Gruber notifications@github.com:
just add them to https://github.com/component/component/wiki/Components, they'll be added to the website by a periodic grabber.
—
Reply to this email directly or view it on GitHub.
component or browserify :P glad to help!
That moment, when being German finally pays off. :D
:D good to close?
is it too much to ask for this to be automated somehow? it just doesn't seem practical to have to add libraries to a markdown sheet for parsing.
Beside of an own registry (which would be a bit against components idea) I believe it may be an option to ask the people at github if they could add some tag support for repos. Then component could use githubs search api.
Am 04.10.2013 um 20:40 schrieb Zachary Adam Kaplan notifications@github.com:
is it too much to ask for this to be automated somehow? it just doesn't seem practical to have to add libraries to a markdown sheet for parsing.
—
Reply to this email directly or view it on GitHub.
@bodokaiser @visionmedia there's clearly a better solution. github's v3 search api allows searching for a specific file.
we can use this api to search for repositories that contain a component.json
.
i like component. let's make it easier for people to use.
+1 for using githubs search api
Am 04.10.2013 um 21:12 schrieb Zachary Adam Kaplan notifications@github.com:
@bodokaiser @visionmedia there's clearly a better solution. github's v3 search api allows searching for a specific file.
we can use this api to search for repositories that contain a component.json.
i like component. let's make it easier for people to use.
—
Reply to this email directly or view it on GitHub.
Oh, we were always wanting to do that. Can you construct an example query looking for component.json at the root level of the repo?
Should be something like:
curl:
curl -H 'Accept: application/vnd.github.preview.text-match+json' https://api.github.com/search/code?q=component.json+in:path
superagent
var superagent = require('superagent');
superagent
.get('https://github.com/search/code')
.set('Accept', 'application/vnd.github.preview.text-match+json')
.query({ q: 'component.json in:path' })
.end(function(err, res) {
if (err) throw err;
console.log(res);
});
What still is missing is another query command to fetch the READMEs (component.json at its own is mostly not quite descriptive)
Okay, definitively worth a test! :)
I'd still prefer GitHub adding tags.
—
Sent from Mailbox for iPhone
On Sat, Oct 5, 2013 at 10:50 AM, Bodo Kaiser notifications@github.com
wrote:
Should be something like:
curl:curl -H 'Accept: application/vnd.github.preview.text-match+json' https://api.github.com/search/code?q=component.json+in:path
superagent
var superagent = require('superagent'); superagent .get('https://github.com/search/code') .set('Accept', 'application/vnd.github.preview.text-match+json') .query({ q: 'component.json in:path' }) .end(function(err, res) { if (err) throw err; console.log(res); });
Reply to this email directly or view it on GitHub:
#56 (comment)