Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
movermeyer
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
movermeyer
8y ago
Discussion on Reddit: https://www.reddit.com/r/programming/comments/8t11z7/readme_...
2.
▲
README badges are vulnerabilities
(movermeyer.com)
2 points
by
movermeyer
8y ago
|
1 comments
3.
▲
by
movermeyer
9y ago
This bot was exclusively applied to repos that were not mine.
4.
▲
by
movermeyer
9y ago
Thanks for reporting this. Firstly, I am sorry for the inconvenience of receiving a broken pull request. I have looked into the pull request and discovered that this is a variant of "Bug #4" from the blog post. It happens when the
5.
▲
by
movermeyer
9y ago
The actual rule is no "excessive automated bulk activity". https://help.github.com/articles/github-terms-of-service/
6.
▲
by
movermeyer
9y ago
The total amount of time to review one of these pull requests can be estimated at < 30 seconds per repo. 30s * 1000 repos = 8h20m. Hardly thousands of hours. But yes, this was a particularly trivial problem to tackle. It was meant to be
7.
▲
by
movermeyer
9y ago
A project I was working on was a much more useful bot. The number of affected repos for that problem was over 35,000 (although 95% of the value from fixing would be gained by only fixing the top 3,000 repos, when weighted by popularity) The
8.
▲
by
movermeyer
9y ago
That's a neat idea. Looks like someone beat me to it though: https://www.namecheap.com/domains/whois/results.aspx?domain=... I've reached out to them to try and see whether they want help. [UPDATE: they&
9.
▲
by
movermeyer
9y ago
Yes, the bot made broken pull requests to some 35 repos before all the issues were ironed out. As a maintainer of those repos, I would be annoyed at these 'corrections'. For my part, I manually corrected all of them and apologized
10.
▲
by
movermeyer
9y ago
Thanks. I've fixed it.
11.
▲
Building bots to mend badges, or how to get your GitHub account suspended
(movermeyer.com)
169 points
by
movermeyer
9y ago
|
67 comments