chore: deploy post build

[mpetrunic]

Alternative to #89

@kalambet I think this makes more sense for this project as it involves fewer build minutes and less of a wait because you don't have to install and build twice.

[kalambet]

@mpetrunic I thought about it before too, but there were two reasons why I initially dismissed it because: (a) not sure if can preserve updating (writing) repo deployments; (b) I wanted to exclude deployment for the draft PRs but leave the CI check. The (b) was not implemented just yet bc I did not check the docs, but tbh same goes with (a) too :)

Do you think it is make sense to preserve deployments and do not deploy to CF Pages on Draft PRs?

[mpetrunic]

@mpetrunic I thought about it before too, but there were two reasons why I initially dismissed it because: (a) not sure if can preserve updating (writing) repo deployments; (b) I wanted to exclude deployment for the draft PRs but leave the CI check. The (b) was not implemented just yet bc I did not check the docs, but tbh same goes with (a) too :)

Do you think it is make sense to preserve deployments and do not deploy to CF Pages on Draft PRs?

Well deployment on its own is "free", and takes very little time 15s. If it's done in a separate job, it's best to cache the build so you avoid reinstalling dependencies and rebuilding.

As for draft, I think you can create if condition that will not execute on draft PRs