feat(app): add flag to commit to signal VSTS CI servers to ignore the…

[marceloavf]

… commit

This avoid VSTS CI servers running another build due to changes related to versioning

ISSUES CLOSED: #54

[coveralls]

Coverage remained the same at 93.469% when pulling 953a789 on marceloavf:feature/allow-vsts-skip-ci into 1373330 on leonardoanalista:master.

[leonardoanalista]

It looks good. Do you think we need a section on readme file explaining the commit skips?
I think we should raise a ticket with Vsts to change their commit slip since they are the only different one.

[marceloavf]

It should help, I only discovered this function after the first test, would it be good to include it in the FAQ section?

There is an issue in vsts-agent #858, also posted it in their ticket system, I really need this to continue my work in VSTS, since it's building twice, I'll open another issue there talking about it there.

[leonardoanalista]

Sure! I merge it now then we track vsts issue. We update readme in separate pr

[marceloavf]

Okay, waiting for the release to test it out, thanks!

[leonardoanalista]

It’s supposed to release automatically after every commit merged into master. I don’t know why it didn’t release. I’ll have to investigate tomorrow

[marceloavf]

No problem, this should help semantic-release/semantic-release#347

[marceloavf]

Seems that the node 8 version have to be the build leader to publish, or use some build stages to make it work properly