feat(ci): PR git actions

[ShaMan123]

I was thinking of adding git actions on PRs:

1. when committing to the PR - build dist and commit to the PR, or use [codesandbox PR builder] ci(): codesandbox #8135 (https://codesandbox.io/docs/ci)
2. when merging to master - checkout dist new build, dist might be out for good
3. lint commit action
4. Code Coverage Summary comment bot - should remove it's prior comment from thread to avoid spamming, [action](https://github.com/marketplace/actions/delete-comment)
5. action to update/build website on release - feat(ci): PR git actions #7593 (comment)

[asturur]

if the git history does not get extremely polluted, that is fine for me. If deleting the branch after merge deletes the history with it.
Not sure if you can checkout dist when merging.

Not sure how the additional commit will eventually trigger new git actions that will trigger another build and so on.
Is the aim to have always a built file available somewhere?

[ShaMan123]

yes it is.
and not to do it manually.
3. lint commit action

[ShaMan123]

https://about.gitlab.com/blog/2018/06/07/keeping-git-commit-history-clean/

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ShaMan123]

a repo with outstanding ci
https://github.com/bubkoo/html-to-image/blob/master/.github/workflows

[asturur]

Label your own issues if you want to avoid the stale bot to bother you

[ShaMan123]

I'm talking about the PR bots they have

[asturur]

i meant this thing here

When you want to rise something you know is worth, give it a label so stale-bot does not come here

[ShaMan123]

great thanks

[ShaMan123]

https://github.com/marketplace/actions/trigger-workflow-and-wait

Triggering updates to fabricjs.com (build_docs) from fabric.js release workflow.
What do you think?