5 ms·

As article says, I wouldn't want hundreds of them. Imagine uploading a simple website, only to have your issue tracker harassed by JSLint bots, HTML validators

by rossy 14y ago

As article says, I wouldn't want hundreds of them. Imagine uploading a simple website, only to have your issue tracker harassed by JSLint bots, HTML validators and pull requests correcting your indentation, replacing <b>s with <em>s etc.

Strilanc 14y ago
Honestly? That sounds amazing (as long as there's a way to manage the noise).
- rossy 14y ago
  I'd much rather use those tools at my own discretion than have them clutter an area of the site where I expect to see feedback from my human users. It would also make GitHub a much more intimidating place to submit code. I don't want those things for my smaller projects.
- jevinskie 14y ago
  So some sort of "plugin" interface where you can opt in to certain bots on a per-repo basis? I could really get behind that! 100% automated and unsolicited? No thank you!
  - technoweenie 14y ago
    Hey, check the Service Hooks tab of your Repository Settings.
    - justincormack 14y ago
      It would be really helpful if each had a short summary when you hover over them as its an awful lot of names which don't mean much. I came across Travis from elsewhere but never would have guessed it was CI from this list.
      - mh- 14y ago
        yeah, +1. I actually cloned the repo so I could peek at the source for the hooks to all these services I'd never heard of. Was easier (lazier) than googling. https://github.com/github/github-services/tree/master/services https://github.com/github/github-services/tree/master/servic...
  - mistercow 14y ago
    Exactly. I think bots are exactly the wrong shape for this task. What would be better would be a framework for automatically processing the files in a git repository and then generating a commit. GitHub could have an interface for uploading them and for applying them to repositories. You could then apply them yourself, or someone else could fork, apply, and then submit a pull request.

by rossy 14y ago

Strilanc 14y ago

Honestly? That sounds amazing (as long as there's a way to manage the noise).

rossy 14y ago
I'd much rather use those tools at my own discretion than have them clutter an area of the site where I expect to see feedback from my human users. It would also make GitHub a much more intimidating place to submit code. I don't want those things for my smaller projects.
jevinskie 14y ago
So some sort of "plugin" interface where you can opt in to certain bots on a per-repo basis? I could really get behind that! 100% automated and unsolicited? No thank you!
- technoweenie 14y ago
  Hey, check the Service Hooks tab of your Repository Settings.
  - justincormack 14y ago
    It would be really helpful if each had a short summary when you hover over them as its an awful lot of names which don't mean much. I came across Travis from elsewhere but never would have guessed it was CI from this list.
    - mh- 14y ago
      yeah, +1. I actually cloned the repo so I could peek at the source for the hooks to all these services I'd never heard of. Was easier (lazier) than googling. https://github.com/github/github-services/tree/master/services https://github.com/github/github-services/tree/master/servic...
- mistercow 14y ago
  Exactly. I think bots are exactly the wrong shape for this task. What would be better would be a framework for automatically processing the files in a git repository and then generating a commit. GitHub could have an interface for uploading them and for applying them to repositories. You could then apply them yourself, or someone else could fork, apply, and then submit a pull request.