From 3ce6795e13d2b4b8ee5ab5b3c9a7130623254eb9 Mon Sep 17 00:00:00 2001 From: Daniel Jancar Date: Sun, 11 Aug 2024 18:41:06 +0200 Subject: [PATCH 1/3] fix --- .github/workflows/release.yml | 2 +- README.md | 2 ++ package.json | 2 +- 3 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 69650f9..09e3deb 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -12,7 +12,7 @@ jobs: - name: Checkout Source Code uses: actions/checkout@v4 with: - fetch-depth: 0 # Ensure full history is fetched + fetch-depth: 0 - name: Sync with Remote run: | diff --git a/README.md b/README.md index e09ec58..60529c1 100644 --- a/README.md +++ b/README.md @@ -96,6 +96,8 @@ We also got some additional features we thought about and couldn't implement yet - **Voting Timeframes**: Users creating a new vote can decide whether there's a start and end date for the votes. - **Multiple Options**: Users can also create votes where multiple options can be selected. +- **Full Test Coverage**: We want to have full test coverage for the platform. +- **Automated Testing**: We already have implemented some automated testing and linting, also in the `release.yml` action, where the app is automatically deployed. If we add full test coverage, we can also add automated testing to the deployment process (spec and e2e tests). # Contributing diff --git a/package.json b/package.json index 787bce7..9736cdf 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@votevault/source", - "version": "0.0.0", + "version": "1.0.0", "license": "MIT", "scripts": { "prepare": "husky" From 3d3f8f1b951f40c224d395940fede598360c98c5 Mon Sep 17 00:00:00 2001 From: Daniel Jancar Date: Sun, 11 Aug 2024 18:44:40 +0200 Subject: [PATCH 2/3] docs: add release action to dev actions docs --- docs/DEV_ACTIONS.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/DEV_ACTIONS.md b/docs/DEV_ACTIONS.md index 342e328..ecdaca9 100644 --- a/docs/DEV_ACTIONS.md +++ b/docs/DEV_ACTIONS.md @@ -33,3 +33,7 @@ ESLint on every pull request and alerts us if there are any errors. The greetings action is a simple action that sends a greeting message to the user that triggered the action. It is used to make the new contributors feel welcome and make them aware of the guidelines and best practices. + +## Release + +We have a fully automated release process that is triggered by a Github Action. The release process is based on the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. The action gets triggered when pushing the latest changes to `master` branch. It publishes a new Github release with the latest changes and updates the `CHANGELOG.md` file, also it publishes the new apps to our servers (Github Pages). From 0cb2d648428d873e1dcd8e29cf0bda6984da1df5 Mon Sep 17 00:00:00 2001 From: Daniel Jancar Date: Sun, 11 Aug 2024 22:34:08 +0200 Subject: [PATCH 3/3] chore: make release workflow push browser files to root --- .github/workflows/release.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 09e3deb..3e944da 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -51,6 +51,12 @@ jobs: if: steps.semantic_release.outputs.new_release == 'true' run: echo "vv.danieljancar.dev" > dist/apps/frontend/CNAME + - name: Move Files Out of browser Folder + if: steps.semantic_release.outputs.new_release == 'true' + run: | + mv dist/apps/frontend/browser/* dist/apps/frontend/ + rmdir dist/apps/frontend/browser + - name: Deploy to GitHub Pages if: steps.semantic_release.outputs.new_release == 'true' run: |