Merge pull request #1 from aditosoftware/migrate-gitlab-to-github

chore: migrate from gitlab to GitHub

Author: rH4rtinger

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Assign the designer team the whole repository
+*   @aditosoftware/devs-designer

.github/ISSUE_TEMPLATE/bug-reports.yml

@@ -0,0 +1,77 @@
+name: Bug Report
+description: File a bug report.
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+
+        ⚠️ Do not share security issues here, instead use the **Report a vulnerability** in the security tab.
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Describe exactly what happened to have this bug appear.
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected Behavior
+      description: Describe what you expect to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction-steps
+    attributes:
+      label: Steps to reproduce
+      description: |
+        Describe the steps to reproduce this bug.
+        This will be automatically formatted into code, so no need for backticks.
+      placeholder: |
+        1.
+        2.
+        3.
+      render: shell
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: Operating System
+      description: What OS are you using?
+      placeholder: Windows 10, macOS 14.6.1, ubuntu 24, ...
+    validations:
+      required: true
+  - type: input
+    id: database-version
+    attributes:
+      label: Database type and version
+      description: What database type and version are you using?
+      placeholder: MariaDB 11.5, PostgreSQL 16.4, ...
+  - type: input
+    id: liquibase-version
+    attributes:
+      label: Liquibase version
+      description: What version of vscode-liquibase are you using?
+      placeholder: 1.0.2
+    validations:
+      required: true
+  - type: input
+    id: vscode-version
+    attributes:
+      label: VSCode version
+      description: What version of VSCode are you using?
+      placeholder: 1.93.0
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,21 @@
+name: Feature Request
+description: Request a new feature.
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to request a new feature!
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the feature here
+    validations:
+      required: true
+  - type: textarea
+    id: implementation-ideas
+    attributes:
+      label: Implementation ideas
+      description: If you have any implementation ideas, you can share them here.

.github/pull_request_template.md

@@ -0,0 +1,12 @@
+
+# Please check before merging
+
+- [ ] Is the content of the `README.md` file still up-to-date?
+- [ ] Have you added an entry to the `CHANGELOG.md`?
+- [ ] Is the pull request title written in the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format?
+- [ ] VSCode: Did you write e2e tests?
+- [ ] VSCode: Did you follow the [UX Guidelines](https://code.visualstudio.com/api/ux-guidelines/overview)?
+
+# Description
+
+Please describe your pull request.

.github/workflows/lint.yml

@@ -0,0 +1,21 @@
+name: ESLint
+
+on:
+  pull_request:
+
+jobs:
+  eslint:
+    name: Run eslint scanning
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      security-events: write
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run ESLint
+        run: npm run lint

.github/workflows/nodejs.yml

@@ -0,0 +1,63 @@
+name: Build Project
+
+on:
+  pull_request:
+
+jobs:
+  build:
+    strategy:
+      matrix:
+        # No windows runner, because in this extension, we have a lot of tests that need docker in the WSL.
+        # Sadly, the setup-wsl (https://github.com/Vampire/setup-wsl) and the current windows runners only support WSL 1.
+        # Therefore, we can not install and start a docker container in the WSL.
+
+        # Currently, no macOS runner, because during the setup of docker, this runner hangs: https://github.com/douglascamata/setup-docker-macos-action/issues/37
+        os: [ubuntu-latest]
+        node-version: [18.x, 20.x, 22.x]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Set up JDK for Liquibase  CLI
+        uses: actions/setup-java@v4
+        with:
+          java-version: 21
+          distribution: temurin
+
+      - name: Check Docker Version
+        run: docker --version
+
+      - name: Check Node.js version
+        run: node -v
+
+      - name: Check npm versions
+        run: npm -v
+
+      - name: Run clean install
+        run: npm ci
+
+      - run: xvfb-run -a npm test
+        if: runner.os == 'Linux'
+      - run: npm test
+        if: runner.os != 'Linux'
+
+      - name: run e2e tests
+        run: xvfb-run -a npm run test:e2e -- --storage ./out/test-resources/${{ matrix.os }}/${{ matrix.node-version }}
+        if: runner.os == 'Linux'
+
+      - name: npm e2e tests
+        run: npm run test:e2e -- --storage ./out/test-resources/${{ matrix.os }}/${{ matrix.node-version }}
+        if: runner.os != 'Linux'
+
+      - name: "Upload e2e screenshots"
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: e2e-screenshots-${{ matrix.os }}-${{ matrix.node-version }}
+          path: ./out/test-resources/**/screenshots/**
+          retention-days: 5
+          if-no-files-found: ignore

.gitlab/merge_request_templates/Default.md

@@ -8,10 +8,6 @@
   },
   // Turn off tsc task auto detection since we have the necessary tasks as npm scripts
   "typescript.tsc.autoDetect": "off",
-  "sonarlint.connectedMode.project": {
-    "connectionId": "SonarQube",
-    "projectKey": "plattform-designer-vscode-liquibase"
-  },
   "workbench.colorCustomizations": {
     "activityBar.activeBackground": "#88d042",
     "activityBar.background": "#88d042",

.npmrc

@@ -4,6 +4,34 @@ All notable changes to the "Liquibase" extension will be documented in this file
 
 The format is based on [Keep a Changelog](http://keepachangelog.com/) and and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## 1.0.2
+
+### Added
+
+- Added repository information to the package.json
+- Added images to README.md
+
+### Changed
+
+- Upgraded dependencies:
+  - @aditosoftware/driver-dependencies to 1.0.4
+  - @aditosoftware/vscode-input to 2.0.1
+  - @aditosoftware/vscode-logging to 1.0.3
+  - immer to 10.1.1
+  - properties-file to 3.5.7
+- Upgraded devDependencies:
+  - @types/chai to 4.3.19
+  - @types/mocha to 10.0.8
+  - @vscode/test-cli to 0.0.10
+  - @vscode/test-electron to 2.4.1
+  - concurrently to 9.0.1
+  - mariadb to 3.3.1
+  - rimraf to 6.0.1
+  - sinon to 19.0.2
+  - vscode-extension-tester to 8.7.0
+  - webpack to 5.94.0
+  - webpack-shell-plugin-next to 2.3.2"
+
 ## 1.0.1
 
 ### Changed

.vscode/settings.json

@@ -25,6 +25,9 @@ You can later edit your configurations with the `Liquibase: Edit existing Liquib
 ### Executing a command
 
 All commands can be accessed from the "Liquibase" item in the status bar.
+
+![Status bar item of Liquibase Extension](/media/walkthrough/statusBar.png)
+
 You can also access all commands by using the the command palette. It can be accessed with the keyboard shortcut <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd> (macOS <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>).
 
 If you execute any command, you notice a general pattern of inputs. You will be always asked the following steps in this order:
@@ -49,7 +52,7 @@ Currently, the following Liquibase commands are supported:
 - [Create Tag](https://docs.liquibase.com/commands/utility/tag.html)
 - [Drop-all](https://docs.liquibase.com/commands/utility/drop-all.html)
 - [Generate Changelog](https://docs.liquibase.com/commands/inspection/generate-changelog.html)
-- [Generate database documentation (db-doc)](https://docs.liquibase.com/commands/utility/db-doc.html) - [more details in this documentation](#generate-database-documentation--getting-an-overview-about-your-database)
+- [Generate database documentation (db-doc)](https://docs.liquibase.com/commands/utility/db-doc.html) - [more details below](#generate-database-documentation--getting-an-overview-about-your-database)
 - [Generate SQL File for incoming changes](https://docs.liquibase.com/commands/update/update-sql.html)
 - [List all deployed changesets (history)](https://docs.liquibase.com/commands/change-tracking/history.html)
 - [List the not deployed changesets (status)](https://docs.liquibase.com/commands/change-tracking/status.html)
@@ -66,6 +69,8 @@ Every command that needs a changelog file, can be executed by right clicking on
 
 Sometimes, you want to have an overview about your whole database. For this, we have a useful command in the status bar labeled _"Overview"_.
 
+![Status bar item for the overview of Liquibase Extension](/media/walkthrough/statusBarOverview.png)
+
 This will create an HTML report with a lot of useful information regarding your database and the changelogs.
 
 You can see information about the current table structure, including columns and indexes.