3 ms·
I get the feeling that there's parts of the community that feel the same way. I'm hoping that the planned move to github will naturally cascade into pre-commit
by wyldfire 10y ago
I get the feeling that there's parts of the community that feel the same way. I'm hoping that the planned move to github will naturally cascade into pre-commit checks.
- ezanmoto 10y agoDo you know of solutions that exist for pre-commit checks for GitHub at the moment?
- wyldfire 10y agoIn general? Yes, Travis CI seems to be a very popular one. Many folks use Appveyor for Windows support AFAICT.
- dikaiosune 10y agoRust uses https://github.com/rust-community/bors https://github.com/rust-community/bors which maintains a linear queue of PRs which can only land after being rebased onto the commits before the PR and subsequently passing tests.
- Joky 10y agoSwift also has a lot of pre-commit CI: - here is the Jenkins bots page: https://ci.swift.org/view/Pull%20Request/ https://ci.swift.org/view/Pull%20Request/ - example of PR test reporting: https://github.com/apple/swift/pull/6802 https://github.com/apple/swift/pull/6802
- WalterBright 10y agodlang uses several. One notable one is the "autotester" written by Brad Roberts. It's built to ensure that breaking the D compiler (as tested by the test suite) does not result in commits. It's incredibly useful.
- Joky 10y agoA big big problem is having enough hardware to have a CI throughput one or two order of magnitude what it is now. Unfortunately that's not an easy thing considering how "heavy" it is to build and test the full toolchain.