summaryrefslogtreecommitdiff
path: root/.rultor.yml
diff options
context:
space:
mode:
authorLasse Schuirmann <lasse.schuirmann@gmail.com>2015-08-04 16:32:16 +0200
committerLasse Schuirmann <lasse.schuirmann@gmail.com>2015-08-04 16:32:16 +0200
commit40d640f6d414446f906359f93d207413eb311bbc (patch)
tree0f068e1271bb73016ffe1a5d4d30fa3bef01831f /.rultor.yml
parentc02e7f6ea6f90f9a945003982b56fd96c7d7a0d7 (diff)
downloadbabel-40d640f6d414446f906359f93d207413eb311bbc.tar.gz
Add rultor configuration
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.
Diffstat (limited to '.rultor.yml')
-rw-r--r--.rultor.yml2
1 files changed, 2 insertions, 0 deletions
diff --git a/.rultor.yml b/.rultor.yml
new file mode 100644
index 0000000..0871296
--- /dev/null
+++ b/.rultor.yml
@@ -0,0 +1,2 @@
+merge:
+ script: echo "Nothing to do (yet)."