fix: use specific commit from theme repo

[Nimrais]

Improving Workflow: Introducing a new update command to streamline theme changes. This enhancement removes the requirement for superficial commits when adjusting the theme, ensuring code integrity and reducing unnecessary access to the theme's repo.

[albertpod]

Why?

[Nimrais]

@albertpod I don't believe it's good practice to modify code behind the scenes. Currently, if we only want to change the theme and not the site content, we're forced to make a superficial commit that doesn't alter any line in this repository but still modifies the site. I'm working on a new update command that will allow changes to the commit without accessing the theme's repo.

[Nimrais]

So the update-theme actions actually will be documented, they will change the commit hash.

[bvdmitri]

we're forced to make a superficial commit that doesn't alter any line in this repository

why? can't you just re-trigger the deployment of the website?

[bvdmitri]

@Nimrais I'm pretty much sure you can just run publish.sh after a change in the theme and there is no need for any superficial commits in the repository.

[Nimrais]

@bvdmitri Yes, you can 100%. And that is exactly the problem. We are deploying from this repo smt that in any sense controlled by this repo.