CI as development companion

[inkdot7]

First, let me admit that I've not read the manuals. Also, I did not do very much r3broot or github coding. So I maybe just did not find the way to do this right...

When I hacked on some changes, it seems that CI building for code developed by users is not very easy, since a user would push to his/her own github repository, where CI is not set up to be done. This means that CI only happens at the point when the user does a full PR.

When developing on other projects, I've found it very useful to have CI builds happens for any branch. With that, it becomes 'feelgood'-boosting to do small commits early, and push to some dummy branch of a repository. Then the CI fires off and rather quickly would notify about breaking changes. Long before thinking about making a PR. Sure, one does local testing too, but the CI machines are just tireless and happily run all tests (for obscure platforms / other experiments / etc...) - every time.

It is like having a development companion. It is of course a rather limited peer in that it does not find overall idea faults - just compile issues and other things that manage to break testing.

So, lots of git add -p, git commit and git push somewhere master:dummy.

Is this doable here as well?