build: changes all workflows to a main/production setup

Author: iOvergaard

.github/workflows/azure-static-web-apps-delightful-beach-055ecb503.yml

@@ -4,18 +4,14 @@ on:
   push:
     branches:
       - main
-      - 'v*/main'
-      - 'v*/dev'
-      - 'v*/contrib'
+      - production
       - 'release/*'
   # This is how azure builds staging environments
   pull_request:
     types: [opened, synchronize, reopened, closed]
     branches:
       - main
-      - 'v*/main'
-      - 'v*/dev'
-      - 'v*/contrib'
+      - production
       - 'release/*'
 
 env:
@@ -44,7 +40,7 @@ jobs:
           app_build_command: 'npm run storybook:build'
           api_location: '' # Api source code path - optional
           output_location: '/storybook-static' # Built app content directory - optional
-          production_branch: 'v1/main' # Production branch
+          production_branch: 'production' # Production branch
           ###### End of Repository/Build Configurations ######
 
   close_pull_request_job:

.github/workflows/chromatic.yml

@@ -16,12 +16,8 @@ on:
       - 'packages/*/lib/**'
       - 'packages/*/assets/**'
     branches-ignore:
-      - 'dependabot/**'
       - 'release/*'
-      - 'Release/*'
-      - 'main'
-      - 'v*/main'
-      - 'v*/release'
+      - 'production'
 
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
@@ -66,6 +62,6 @@ jobs:
           exitOnceUploaded: true
           onlyChanged: true,
           untraced: '.storybook/images/**/*,storyhelpers/**/*'
-          autoAcceptChanges: 'v*/contrib'
+          autoAcceptChanges: 'main'
           externals: |
             .storybook/images/**

.github/workflows/codeql-analysis.yml

@@ -4,17 +4,11 @@ on:
   push:
     branches:
       - main
-      - dev
-      - 'v*/dev'
-      - 'v*/main'
-      - 'v*/contrib'
       - 'release/*'
   pull_request:
     # The branches below must be a subset of the branches above
     branches:
-      - dev
-      - 'v*/dev'
-      - 'v*/contrib'
+      - main
       - 'release/*'
   schedule:
     - cron: '39 20 * * 3'

.github/workflows/publish.yml

@@ -3,18 +3,10 @@ name: Publish
 on:
   push:
     branches:
-      - main
-      - 'v*/main'
+      - production
 
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
-    inputs:
-      sha:
-        description: The commit hash referring to the commit to check.
-        required: false
-      ref:
-        description: The head branch associated with the pull request.
-        required: false
 
 env:
   NODE_OPTIONS: --max_old_space_size=16384

.github/workflows/tests.yml

@@ -5,7 +5,7 @@ on:
   # Triggers the workflow on push or pull request events but only for the dev branch
   pull_request:
     branches-ignore:
-      - 'v*/main'
+      - production
 
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:

README.md

@@ -144,5 +144,5 @@ See the rest of [the scripts here](docs/SCRIPTS.md).
 - 📥 Pull requests and 🌟 Stars are always welcome.
 - Read our [contributing guide](docs/CONTRIBUTING.md) to get started.
 - Please report bugs and feature requests in the [issue tracker](https://github.com/umbraco/Umbraco.UI/issues)
-- The main branch is the latest development branch. Please make your pull requests against this branch: `v1/contrib`
-  - You can see the latest features in the Storybook attached to this branch: [v1/contrib](https://delightful-beach-055ecb503-v1contrib.westeurope.azurestaticapps.net/)
+- The main branch is the latest development branch. Please make your pull requests against this branch: `main`
+  - You can see the latest features in the Storybook attached to this branch: [main](https://delightful-beach-055ecb503-main.westeurope.azurestaticapps.net/)

docs/RELEASE_INSTRUCTION.md

@@ -2,23 +2,23 @@
 
 1. Create a new branch for the release. We need a good naming convention: `release/<Version>` (example: `release/1.12.0`).
 1. Review new release PR (either [on GitHub](https://github.com/umbraco/Umbraco.UI/compare/)).
-1. Make a PR from the new branch to the `main` branch.
 1. Run `npm run lerna:version` and Lerna will suggest a version bump for each package.
 1. Review the new version numbers and accept with `y` and Lerna will now bump each package and update the local CHANGELOG.md file using descriptions from the conventional commits, Lerna will also reinstall NPM and generate a new lockfile.
    1. We are continuously improving the way Lerna detects changes, so you may run into packages being bumped and you do not know why. It is okay to publish a package that has not been changed in order not to mess too much with the logic that Lerna uses to detect changes.
 1. Push all the changes to your release branch.
-1. Make a PR from the new branch to the `main` branch.
+1. Make a PR from the new branch to the `production` branch.
 1. Add the `ignore-for-release`-label to the PR.
 1. Wait for GitHub checks to pass.
 1. Github will post a comment with a test link to try out that the release works in Storybook. Please check that it works.
-1. Merge PR into main **using the Merge strategy** (very important so the history is not mangled) - this will trigger two actions - `Publish`, and `Azure Static Web Apps CI/CD`. The `Publish` workflow is responsible for publishing packages to NPM. It will only publish the packages that have higher version that previously published ones. The azure workflow will build and publish UI library Storybook.
-1. Merge the `v1/main` branch with the `v1/contrib` branch by writing `git merge origin/main` and then push the changes.
+1. Merge PR into production **using the Merge strategy** (very important so the history is not mangled) - this will trigger two actions - `Publish`, and `Azure Static Web Apps CI/CD`. The `Publish` workflow is responsible for publishing packages to NPM. It will only publish the packages that have higher version that previously published ones. The azure workflow will build and publish UI library Storybook.
+1. Merge the `production` back into the `main` branch by writing `git merge origin/production` when on the `main` branch, and then push the changes. (This way we ensure that the `main` branch is always up to date with the latest release and accompanying release notes).
 1. Go to Github and [create a new release](https://github.com/umbraco/Umbraco.UI/releases/new).
    1. Using tags on the release, we want to target `vx.x.x` where "x.x.x" is the version number that the UUI package was bumped to during the release.
    1. Select the prevous version, in relation to your release, in `Previous tag` and press `Generate release notes`.
    1. Check the generated release notes, see if PRs are in the right category, if not append labels to them and return to generate again.
 1. The UI Library has now been updated.
-1. Write an post on the UI Library Slack Channel evt. update Backoffice.
+1. Write an post on the UI Library Slack Channel.
+1. Consider when to update the Backoffice.
 
 ## How to clear tags
 

package.json

@@ -152,7 +152,7 @@
     "*": "prettier --ignore-unknown --write"
   },
   "storybook": {
-    "url": "https://v1-contrib--62189360eeb21b003ab2f4ad.chromatic.com/"
+    "url": "https://uui.umbraco.com"
   },
   "packageManager": "[email protected]"
 }

packages/uui/package.json

@@ -130,6 +130,6 @@
     "access": "public"
   },
   "storybook": {
-    "url": "https://v1-contrib--62189360eeb21b003ab2f4ad.chromatic.com/"
+    "url": "https://uui.umbraco.com"
   }
 }