Fix merge pipeline

[RobinWijnant]

See reopened issue #6

• Removing the execution away from the container is a possible fix for the failing git commit
• tsc --build or tsc -b is used to only update the changed files. The dist is always deleted so adding this flag is redundant. The verbose flag is also not needed imo.

Closes #6

[RobinWijnant]

The failing git commit is caused by the EndBug/add-and-commit action. I have opened an issue on the repo. See EndBug/add-and-commit#27

[bramvanhoutte]

Is there really not another way of deploying the docs? Because now the PR is always going to be cluttered with the built documentation files

[RobinWijnant]

What do you mean with cluttered? Is the automatic commit bothering you? What do you propose?

[bramvanhoutte]

Right now there are 43 changes. But these are generated build files, meaning they will change every time a new build is done. This means that every pull request will have 40+ changes, which is really annoying to filter through when reviewing.

[RobinWijnant]

Normally the commit with the generated doc folder only occurs after the merge in master. I wanted to test if it worked without waiting for the merge. This leaded to the docs already being commited in this branch. I think this was confusing.

I removed the generated docs from this branch.

I am also thinking of using a special branch to publish the docs to. It will help keeping a clean commit history on master. What do you think?

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀