Skip to content
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

Become a github tool #29

Open
alexanderepstein opened this issue Jul 4, 2017 · 6 comments
Open

Become a github tool #29

alexanderepstein opened this issue Jul 4, 2017 · 6 comments

Comments

@alexanderepstein
Copy link

alexanderepstein commented Jul 4, 2017

I would love to use this as a tool for most of my repositories even the ones that are not written in js.
Would it be possible to transform this tool into something that would appear here https://github.com/marketplace similar to the Travis CI or Codacy.

For example I would love to use this to get updates on bundlesize in a repository with shell scripts but don't want to add node modules to the project just to accomplish this (just adds to the bundlesize I am trying to keep as low as possible).

@siddharthkp
Copy link
Owner

That's a very interesting point. I will definitely look into it.

@siddharthkp
Copy link
Owner

Whoops, they turned it down.

This is from the docs:

OAuth Apps should have a minimum of 1000 users.
GitHub Apps should have a minimum of 250 installations.

@alexanderepstein
Copy link
Author

Huh I don't understand according to your npm statistics you seem to meet both of these requirements. 7,150 downloads in the last month.

@siddharthkp
Copy link
Owner

siddharthkp commented Aug 1, 2017

Sadly, downloads does not equate proportionally to users.

bundlesize is a oauth app right now with a lot less than 1000 users.

I probably should convert it into a github app because 250 installations is an easier target. To be honest, it doesn't really help in the setup (because of the manual CI variables step). But, to be featured on the marketplace would be pretty cool.

@Daniel15
Copy link
Contributor

Daniel15 commented Sep 6, 2017

Huh I don't understand according to your npm statistics you seem to meet both of these requirements. 7,150 downloads in the last month.

For what it's worth, number of npm downloads is not a very good measure of popularity. Poorly-configured CI systems will download dependencies fresh on every single build, so the build of one single project can result in hundreds or thousands of downloads of a package per month, even if there's only a few people working on it.

@siddharthkp
Copy link
Owner

@Daniel15 Yep, vanity metrics 😄

I track repos separately, that's the one true metric that matters for me

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

No branches or pull requests

3 participants