chore(releases): add workflow for releasing old documentation #1764
Conversation
gfellerph
requested review from
oliverschuerch,
alizedebray and
imagoiq
as code owners
|
|
Preview environment ready: https://preview-1764--swisspost-web-frontend.netlify.app |
| echo "site_id=$site_id" >> $GITHUB_OUTPUT | ||
| echo "branch_version=$branch_version" >> $GITHUB_OUTPUT | ||
|
|
||
| # Tries to create a new netlify site. If the site with this version already exists, the job will fail |
There was a problem hiding this comment.
We could get around the failing job, if we would use netlify sites:list first:
https://cli.netlify.com/commands/sites
|
Kudos, SonarCloud Quality Gate passed!
|
|
Kudos, SonarCloud Quality Gate passed!
|
|
Closing as not relevant anymore, will be superseded by a better workflow. |
gfellerph
deleted the
1430-workflow-for-releasing-patch-updates-for-older-versions
branch
This workflow takes care of a few things. Old releases live as their own site on netlify. On the current documentation, we redirect e.g. /v4 to the old documentation site. The branch name is important and should always follow the format
release/v[major release]->release/v3.Disclaimer: In order to test this workflow, it needs to be on main.