Open steffansluis opened 10 years ago
Agree. Good point
Maybe we should split up the Gruntfile before we do this. It's getting pretty big because it contains all the task definitions, which have little to do with each other and are perfectly capable of living in separate files in a config folder. It would also allow us to have the same Gruntfile on every branch while selectively enabling tasks by adding them to the version control for that branch.
We should set up a seperate grunt config for the gh-pages branch that will automatically build coverage and complexity reports and documentation, as well as examples. We can use the gitignore file to exclude the src files from the branch on GitHub while still having them available locally to build source and documentation. We can then automate the building of the gh-pages additions through Travis. Since this automates the updating of docs and code analysis it also improves workflow :)