Hello,

The typical workflow for changes that need to be pushed immediately online
is:
* commit to master
* cherry-pick to site
* docker build from site
* commit to website

Normally any change that appears online in the website should be also
committed in the site branch of our repo and in most case we shall never
update the website repo directly.

As I was trying to update the website recently I noticed that there is a
mixture of all kind of commits which does not facilitate the process. In
the end, I abandoned since I didn't want to cause more confusion.

While waiting for the automated builds of the website (thanks Francis:))
let's try to keep the workflow clean.

Best,
Stamatis

Reply via email to