Re:Building bots to mend badges, or how to get your GitHub a...
by d0lph on Thursday March 08, 2018 @02:58PM
(#16547154)
The automation wouldn't be doing anything unsolicited either, since it's only doing things that have been defined in the UI.
Perhaps they didn't mean automation per se, but CI is certainly automation, automatic merging, as in not manually merged by a human.
Perhaps a better rule would have been, no automation on repos not controlled by yourself.
Re:Building bots to mend badges, or how to get your GitHub a...
by movermeyer on Thursday March 08, 2018 @03:44PM
(#16547477)
The actual rule is no "excessive automated bulk activity".
Re:Building bots to mend badges, or how to get your GitHub a...
by d0lph on Thursday March 08, 2018 @03:54PM
(#16547548)
That being the case, seems like OP's bot probably should have been allowed, especially since it seemed like they were only automating their repos.
Re:Building bots to mend badges, or how to get your GitHub a...
by movermeyer on Friday March 09, 2018 @06:24AM
(#16551059)
This bot was exclusively applied to repos that were not mine.
Re:Building bots to mend badges, or how to get your GitHub a...
by michaelmior on Thursday March 08, 2018 @04:30PM
(#16547785)
If it's defined in the UI, it doesn't make it unsolicited. I can go to any repository for someone I've never heard of and make a PR as a human. That is still unsolicited. I think the concern is the combination of unsolicited and automated.
I just don't think there's any meaningful claim that CI explicitly configured by maintainers using officially supported channels should be lumped in the same category as automated scraping of repositories for creating PRs.
Sure, there are many definitions of automation that would include both of these things, but I think it's obvious what GitHub intends in practice.