delta/babel.git - github.com: mitsuhiko/babel.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove unused tool configuration	Aarni Koskela	2022-01-25	1	-12/+0
\|
*	rultor: Remove test execution	Lasse Schuirmann	2015-09-24	1	-3/+1
\| \| \| \| \| \|	Something's wrong here and we do need to debug that first. So in order for us being able to do rultor merges, let's just not execute tests for now.
*	rultor: Run tests on merge	Lasse Schuirmann	2015-09-22	1	-1/+11
\| \| \| \| \| \|	This will revalidate a PR at least naively (i.e. only for one platform and python version) right before doing the actual merge and thus may prevent breaking master.
*	rultor: Linearize commit history on merge	Lasse Schuirmann	2015-09-22	1	-0/+2
\| \| \| \| \|	This will make rultor rebase a PR and then fastforwarding the master branch if a merge action is requested.
*	Add rultor configuration	Lasse Schuirmann	2015-08-04	1	-0/+2
	This allows merging via github comments. The comment `@rultor merge` will execute the script (which currently doesn't do anything) and if it succeeds will perform the merge. I plan to use rultor later for: * Automatic deployment to PyPI (development releases directly from master, we do this already in coala, see https://github.com/coala-analyzer/coala/blob/master/.rultor.yml) * Automatic releasing with deployment to PyPI. * Veryfy that all CI services pass before merging (see https://github.com/yegor256/rultor/issues/869) With this any manual pushes to master are disallowed, all pushes to master have to be validated by continuous integration and reviewed by a non-committer.