Merge branch 'develop' into refactor/fix-delete-icon-css

samply · May 21, 2024 · edb4c94 · edb4c94
2 parents 829b605 + b7027ba
commit edb4c94
Show file tree

Hide file tree

Showing 19 changed files with 595 additions and 152 deletions.
diff --git a/.github/ISSUE_TEMPLATE/1-feature-request.yml b/.github/ISSUE_TEMPLATE/1-feature-request.yml
@@ -0,0 +1,51 @@
+name: Feature request
+description: Suggest an idea for this project
+title: "[Feature]: "
+body:
+  - type: textarea 
+    id: summary
+    attributes:
+      label: General Summary
+      description: Please provide a general summary of the problem
+      placeholder: e.g. "The main issue is that..."
+    validations:
+      required: true
+  - type: textarea
+    id: change 
+    attributes:
+      label: Suggested Change
+      description: Provide details on the suggested change
+      placeholder: e.g. "This new feature will allow users to update..."
+    validations:
+      required: true
+  - type: dropdown
+    id: breaking
+    attributes:
+      label: Is this Breaking?
+      description: Explain the behavior expected in this case
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
+  - type: textarea 
+    id: current_behavior
+    attributes:
+      label: Current Behavior
+      description: Explain what the current behavior is
+    validations:
+      required: true
+  - type: textarea
+    id: new_behavior
+    attributes:
+      label: New Behavior
+      description: Propose what the new behavior would be
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Detailed Description
+      description: Please provide a more detailed description
+    validations:
+      required: false 
diff --git a/.github/ISSUE_TEMPLATE/2-bug-report.yml b/.github/ISSUE_TEMPLATE/2-bug-report.yml
@@ -0,0 +1,58 @@
+name: Bug Report
+description: Report a bug to improve Lens
+title: "[Bug]: "
+body:
+  - type: textarea 
+    id: summary
+    attributes:
+      label: General Summary
+      description: Please provide a general summary of the problem
+      placeholder: e.g. "The main issue is that..."
+    validations:
+      required: true
+  - type: textarea 
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: Explain the behavior expected
+      placeholder: e.g. "The feature should do a, then b when you click c."
+    validations:
+      required: true
+  - type: textarea 
+    id: current
+    attributes:
+      label: Current Behavior
+      description: Explain what the actual behavior is
+      placeholder: e.g. "The feature actually does x, y and shows error z."
+    validations:
+      required: true
+  - type: textarea
+    id: possible_solution
+    attributes:
+      label: Possible Solution
+      description: Suggest a possible fix for the bug
+    validations:
+      required: false
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: Explain how to reproduce the problem
+      placeholder: e.g. "1. The first step to reproduce this error is to access the members area..."
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Context (Environment)
+      description: Provide context on the setting and environment
+      placeholder: e.g. "This bug happened on a Windows 10 PC running the newest Google Chrome."
+    validations:
+      required: false 
+  - type: textarea
+    id: description
+    attributes:
+      label: Detailed Description
+      description: Please provide a more detailed description
+    validations:
+      required: false 
diff --git a/.github/ISSUE_TEMPLATE/3-vulnerability-report.yml b/.github/ISSUE_TEMPLATE/3-vulnerability-report.yml
@@ -0,0 +1,48 @@
+name: Vulnerability Report
+description: Report a potential software vulnerability
+title: "[Vulnerability]: "
+body:
+  - type: textarea 
+    id: summary
+    attributes:
+      label: General Summary
+      description: Please provide a general summary of the problem
+      placeholder: e.g. "An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server."
+    validations:
+      required: true
+  - type: textarea 
+    id: component
+    attributes:
+      label: Effected Component(s)
+      description: List the components effected by this vulnerability
+    validations:
+      required: true
+  - type: textarea 
+    id: impact 
+    attributes:
+      label: Impact of Vulnerability
+      description: Describe the scope of the vulnerability's impact
+    validations:
+      required: true
+  - type: textarea
+    id: remediation
+    attributes:
+      label: Possible Remediation
+      description: Propose a remediation suggestion if you have one.
+      validations:
+      required: false
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: Explain how to reproduce the problem
+      placeholder: e.g. "1. The first step to reproduce this error is to access the members area..."
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Detailed Description
+      description: Please provide a more detailed description
+    validations:
+      required: false 
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -0,0 +1,24 @@
+### General Summary
+
+### Description
+<!--- Describe changes in detail -->
+
+### Related Issue
+<!--- Please link to the issue here: -->
+
+---
+
+### Motivation and Context
+
+### How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+
+### Screenshots (if appropriate):
+
+---
+
+<!--- Please check if the PR fulfills these requirements -->
+- [ ] The commit message follows guidelines
+- [ ] Tests for the changes have been added
+- [ ] Documentation has been added/ updated
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -8,17 +8,60 @@ jobs:
   build-and-publish:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
+      - name: "Checkout Code"
+        uses: actions/checkout@v3
+      - name: "Setup NodeJS with cache (if available)"
+        uses: actions/setup-node@v3
         with:
           node-version: 20
           registry-url: 'https://registry.npmjs.org'
           cache: 'npm'
-      - run: npm ci
+      - name: "Download dependencies"
+        run: npm ci
       - name: "Build @samply/lens"
         run: npm run build
       - name: "Publish @samply/lens"
         run: npm publish --access public
         env:
           NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
 
+  release:
+    needs: build-and-publish
+    runs-on: ubuntu-latest
+    steps:
+      - name: "Checkout Code"
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: "Update CHANGELOG"
+        id: changelog
+        uses: requarks/changelog-action@v1
+        with:
+          token: ${{ github.token }}
+          tag: ${{ github.ref_name }}
+
+      - name: "Create Release"
+        uses: ncipollo/release-action@v1
+        with:
+          allowUpdates: true
+          draft: false
+          makeLatest: true
+          name: ${{ github.ref_name }}
+          body: ${{ steps.changelog.outputs.changes }}
+          token: ${{ github.token }}
+
+      - name: "Commit CHANGELOG.md"
+        uses: stefanzweifel/git-auto-commit-action@v4
+        with:
+          branch: main
+          commit_message: 'docs: added changelog for ${{ github.ref_name }} [skip ci]'
+          file_pattern: CHANGELOG.md
+
+      - name: "Create PR for syncing back changelog"
+        uses: peter-evans/create-pull-request@v6
+        with:
+          title: "Sync develop with main"
+          body: "For easy synchronisation of main with develop, triggered by the [release workflow](./.github/workflows/release.yml). Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action."
+          branch: "automated-pr/sync-main-to-develop"
+          base: "develop"
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -6,11 +6,8 @@ services:
     command:
       - --entrypoints.web.address=:80
       - --entrypoints.websecure.address=:443
-      - --entrypoints.web.http.redirections.entrypoint.to=websecure
-      - --entrypoints.web.http.redirections.entrypoint.scheme=https
       - --providers.docker=true
       - --providers.docker.exposedbydefault=false
-      - --providers.file.directory=/conf/
       - --accesslog=true
     ports:
       - "80:80"

diff --git a/docs/GIT_FLOW.md b/docs/GIT_FLOW.md
@@ -42,104 +42,3 @@ Please see **[Semantic Versioning](https://semver.org/)**
 **SemVer** -> fix type commits should be translated to PATCH releases. feat type commits should be translated to MINOR releases. Commits with BREAKING CHANGE in the commits, regardless of type, should be translated to MAJOR releases.
 
 See more: [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#specification)
-
-## Issues Templates:
-
-### Bug report
-
-```
-## General Summary
-
-## Expected Behavior
-
-## Current Behavior
-
-## Possible Solution
-<!--- Suggest a fix/reason for the bug (optional) -->
-
-## Steps to Reproduce
-<!--- Provide a link to a live example if possible -->
-1.
-2.
-3.
-4.
-
-## Context (Environment)
-
-## Detailed Description
-
-## Possible Implementation
-```
-
-### Feature request
-
-```
-## Suggested Change
-<!--- What kind of change does this PR introduce? -->
-
-## Is This Breaking?
-<!--- Does this PR introduce a breaking change? -->
-
-## Current Behavior
-
-## New Behavior
-
-## Detailed Description
-
-```
-
-### Vulnerability report
-
-```
-# Vulnerability Report
-
-I identified potential security vulnerabilities in [Component].
-
-## Summary
-<!--- Short summary: E.g. An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server. -->
-
-## Component
-
-## Impact
-
-## Remediation
-<!--- Propose a remediation suggestion if you have one. Make it clear that this is just a suggestion, as the maintainer might have a better idea to fix the issue. -->
-
-## Steps to Reproduce
-<!--- Provide a link to a live example if possible -->
-1.
-2.
-3.
-4.
-
-## Detailed Description
-<!--- Give all details on the vulnerability; especially the code -->
-
-```
-
-## PR Template
-```
-<!--- Please check if the PR fulfills these requirements -->
-- [ ] The commit message follows guidelines
-- [ ] Tests for the changes have been added
-- [ ] Documentation has been added/ updated
-
-## General Summary
-
-## Description
-<!--- Describe changes in detail -->
-
-## Related Issue
-<!--- Please link to the issue here: -->
-
-## Motivation and Context
-
-## How Has This Been Tested?
-<!--- Please describe in detail how you tested your changes. -->
-<!--- Include details of your testing environment, and the tests you ran to -->
-
-## Screenshots (if appropriate):
-```
-
-For reference: *[Using templates](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)*
-
diff --git a/package-lock.json b/package-lock.json