search

OData / odataorg.github.io

Staging site and collaboration repository for http://www.odata.org
MIT License
63 stars 101 forks source link

Add GitHub action workflow for publishing OData org website to production #353

Closed gathogojr closed 1 year ago

gathogojr commented 1 year ago

Add GitHub action workflow for publishing OData org website to production

gathogojr commented 1 year ago

So, when we push to the master branch, the site will be deployed to both staging and production concurrently?

Is there any difference between this workflow yml and the staging yml other than the fact that the staging workflow has the extra slot-name: 'stage' property on the Deploy to Azure Web App step? If not, then maybe we could have just one workflow that includes to two deploy steps, one to staging and another to prod.

But I'm curious whether the staging workflow is of any value if we'll deploy both to staging and production at the same time.

My thoughts were to do another PR to modify the staging workflow such that it's triggered manually if/when necessary. Come to think of it, would it make sense to modify both workflows such that they're triggered manually?

Another thing I considered is having a "live" branch (like we do in MicrosoftDocs repo) that we'd be rebasing with latest changes in "master" branch whenever we want to deploy the site - as opposed to deploying from master branch automatically when PRs are merged.