Updated config files and github actions

Author: jskonst

.github/workflows/onlineshop_backend.yml

@@ -0,0 +1,26 @@
+name: Python package
+
+on: [push,  pull_request]
+
+jobs:
+  backend:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Setup node
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18.16.x
+          cache: yarn
+          cache-dependency-path: ./onlineshop/source/server/yarn.lock
+      - name: Lint backend
+        run: |
+          cd ./onlineshop/source/server/
+          yarn install --immutable --immutable-cache --check-cache
+          yarn run lint
+      - name: Test server
+        run: |
+          cd ./onlineshop/source/server/
+          yarn install --immutable --immutable-cache --check-cache
+          yarn run test

.github/workflows/onlineshop_frontend.yml

@@ -0,0 +1,26 @@
+name: Python package
+
+on: [push,  pull_request]
+
+jobs:
+  frontend:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Setup node
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18.16.x
+          cache: yarn
+          cache-dependency-path: ./onlineshop/source/client/yarn.lock
+      - name: Lint frontend
+        run: |
+          cd ./onlineshop/source/client/
+          yarn install --immutable --immutable-cache --check-cache
+          yarn run lint
+      - name: Test client
+        run: |
+          cd ./onlineshop/source/client/
+          yarn install --immutable --immutable-cache --check-cache
+          yarn run test

.github/workflows/rpgsaga.yml

@@ -0,0 +1,27 @@
+name: golangci-lint
+on: [push,  pull_request]
+
+jobs:
+  saga-ci:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Setup node
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18.16.x
+          cache: yarn
+          cache-dependency-path: ./rpgsaga/saga/yarn.lock
+      - name: Lint Saga
+        run: |
+          cd ./rpgsaga/saga
+          yarn install --immutable --immutable-cache --check-cache
+          yarn run test
+      - name: Test Saga
+        run: |
+          cd ./rpgsaga/saga
+          yarn install --immutable --immutable-cache --check-cache
+          yarn run test
+        
+         

.gitlab-ci.yml

@@ -1,9 +1,9 @@
-stages:
-  - lint_saga
-  - test_saga
-  - lint_shop
-  - test_shop
-
-include:
-  - local: /rpgsaga/.gitlab-ci.yml
+stages:
+  - lint_saga
+  - test_saga
+  - lint_shop
+  - test_shop
+
+include:
+  - local: /rpgsaga/.gitlab-ci.yml
   - local: /onlineshop/.gitlab-ci.yml

.gitlab/issue_templates/Learning.md

@@ -1,12 +1,12 @@
-Activities:
-- [ ] todo
-
-Reviewers: Bootcamp LT
-
-Exit Criteria:
-- All Checkboxes are marked
-- Bootcamp LT have posted in this issues a comment with sign off that the issue is fully done
-
-Next Task: #
-
-/estimate 1d
+Activities:
+- [ ] todo
+
+Reviewers: Bootcamp LT
+
+Exit Criteria:
+- All Checkboxes are marked
+- Bootcamp LT have posted in this issues a comment with sign off that the issue is fully done
+
+Next Task: #
+
+/estimate 1d

.gitlab/issue_templates/RPGSaga.md

@@ -1,20 +1,20 @@
-**Goal:**
-* Practice with C# exam topic ""
-
-**Activities:**
-- [ ] 
-- [ ] 
-- [ ] 
-- [ ] 
-- [ ] (optional)
-- [ ] (optional)
-
-**Reviewers:** Mentor or Bootcamp LT
-
-**Acceptance Criteria:**
-- All mandatory checkboxes are marked;
-- The reviewer has approved your merge request created with the changes.
-
-**Next Task:** #
-
-/estimate 4h
+**Goal:**
+* Practice with C# exam topic ""
+
+**Activities:**
+- [ ] 
+- [ ] 
+- [ ] 
+- [ ] 
+- [ ] (optional)
+- [ ] (optional)
+
+**Reviewers:** Mentor or Bootcamp LT
+
+**Acceptance Criteria:**
+- All mandatory checkboxes are marked;
+- The reviewer has approved your merge request created with the changes.
+
+**Next Task:** #
+
+/estimate 4h

.gitlab/issue_templates/User Story.md

@@ -1,36 +1,36 @@
-#### Use cases
-
-(description of use cases from end-user point of view, e.g.: As a sales person I want to ...)
-
-#### Motivation
-
-(describe what is behind the use cases and what value this user value gives us from users point of view)
-
-#### Acceptance Criteria
-
-(list of Acceptance Criteria)
-
-#### Design
-
-(Mockups, links to design etc.)
-
-#### Checklist
-
-- [ ] Mockups/icons/spec are provided
-- [ ] Messages for tooltips/errors/validations/placeholders/popups etc. are provided
-- [ ] Possible UI element states and their transitions are described, e.g. which elements can be disabled and under which conditions
-- [ ] Default values are provided
-- [ ] Validation is described: max/min length, required/optional fields
-- [ ] Sorting/filtering options are described
-- [ ] Are any changes upon upgrade required
-- [ ] Performance requirements (max time an operation should take, any need to show a spinner if it takes more time)
-- [ ] Low priority tasks are highlighted (what AC can be tagged as 'nice to have' and should have lower priority over others)
-
-#### Test cases
-
-(link to test cases; provided by QA once they are ready)
-
-#### Affected areas
-
-(Filled when the issue is resolved by developer; if possible, specify features/pages/controls that might be broken due to changes introduced in the MR. Try to be as
-specific as possible so that QA does not have to re-test the whole feature.)
+#### Use cases
+
+(description of use cases from end-user point of view, e.g.: As a sales person I want to ...)
+
+#### Motivation
+
+(describe what is behind the use cases and what value this user value gives us from users point of view)
+
+#### Acceptance Criteria
+
+(list of Acceptance Criteria)
+
+#### Design
+
+(Mockups, links to design etc.)
+
+#### Checklist
+
+- [ ] Mockups/icons/spec are provided
+- [ ] Messages for tooltips/errors/validations/placeholders/popups etc. are provided
+- [ ] Possible UI element states and their transitions are described, e.g. which elements can be disabled and under which conditions
+- [ ] Default values are provided
+- [ ] Validation is described: max/min length, required/optional fields
+- [ ] Sorting/filtering options are described
+- [ ] Are any changes upon upgrade required
+- [ ] Performance requirements (max time an operation should take, any need to show a spinner if it takes more time)
+- [ ] Low priority tasks are highlighted (what AC can be tagged as 'nice to have' and should have lower priority over others)
+
+#### Test cases
+
+(link to test cases; provided by QA once they are ready)
+
+#### Affected areas
+
+(Filled when the issue is resolved by developer; if possible, specify features/pages/controls that might be broken due to changes introduced in the MR. Try to be as
+specific as possible so that QA does not have to re-test the whole feature.)

.gitlab/merge_request_templates/Merge Request.md

@@ -1,38 +1,38 @@
-### Issue item link
-
-`#issue_num and issue name`
-
-### Description
-
-#### What/Why
-
-`Describe what needs to be done`
-
-#### How
-
-`Describe what you did`
-
-#### Result
-
-`Describe the result/output of your work  (e.g. screenshot/gif)`
-
-#### Other work
-
-`!specify other work if there's one!`
-
-#### Checklist
-
-- [ ] _Have you specified the name of the issue in MR name?_
-- [ ] _Have you pulled down the code?_
-- [ ] _Have you alpha tested your code 
-- [ ] _have you specified Affected areas in the related issue item_
-- [ ] _Does the code build and do the tests pass for you locally?_
-- [ ] _Does migration scripts (if any) committed to the repo?_
-- [ ] _Does this code allows us to achieve some Acceptance Criteria (task requirements)?_
-- [ ] _Have any_ `dev` _branch changes been merged up into this branch?_
-- [ ] _Have you confirmed that no warnings or errors upon compilation have been introduced?_
-- [ ] _Have you confirmed that no warnings or errors in the browser console have been introduced?_
-- [ ] _Have you warn the team lead about necessity of running migration script on dev/stage environment?_
-- [ ] _Have the appropriate unit/integration/UI tests been written?_
-- [ ] _Have **discussed** and **filed new issue** if found some bugs that out of the scope of my issue_
-- [ ] _Have **tested** code and verified that there is no regression_
+### Issue item link
+
+`#issue_num and issue name`
+
+### Description
+
+#### What/Why
+
+`Describe what needs to be done`
+
+#### How
+
+`Describe what you did`
+
+#### Result
+
+`Describe the result/output of your work  (e.g. screenshot/gif)`
+
+#### Other work
+
+`!specify other work if there's one!`
+
+#### Checklist
+
+- [ ] _Have you specified the name of the issue in MR name?_
+- [ ] _Have you pulled down the code?_
+- [ ] _Have you alpha tested your code 
+- [ ] _have you specified Affected areas in the related issue item_
+- [ ] _Does the code build and do the tests pass for you locally?_
+- [ ] _Does migration scripts (if any) committed to the repo?_
+- [ ] _Does this code allows us to achieve some Acceptance Criteria (task requirements)?_
+- [ ] _Have any_ `dev` _branch changes been merged up into this branch?_
+- [ ] _Have you confirmed that no warnings or errors upon compilation have been introduced?_
+- [ ] _Have you confirmed that no warnings or errors in the browser console have been introduced?_
+- [ ] _Have you warn the team lead about necessity of running migration script on dev/stage environment?_
+- [ ] _Have the appropriate unit/integration/UI tests been written?_
+- [ ] _Have **discussed** and **filed new issue** if found some bugs that out of the scope of my issue_
+- [ ] _Have **tested** code and verified that there is no regression_

.vscode/settings.json

@@ -0,0 +1,7 @@
+{
+    "files.exclude": {
+        "rpgsaga": true,
+        "codewars": true,
+        "onlineshop": true,
+    }
+}

README.md

@@ -1,28 +1,12 @@
-# How to Work with this Project
-
-This project is your Portfolio: your future interviewer will take a look at that repo and pay attention to:
-1. Repository Quality (Source Code, Branches, Commits, READMEs, etc.)
-1. Issues/Board/Milestones (how many issues/milesones were closed, tickets management quality, etc.)
-1. Merge Requests (overall MRs qualry, all MRs must be reviewed and approved, etc.)
-
-If you have any blockers or questions please feel free to ping both Bootcamp LT or PT Mentor (depends on what task you are currently doing).
-
-As output of your learning on Bootcamp you should have 3 folders:
-1. codewars 
-1. rpgsaga
-1. onlineshop
-
-For RpgSaga and online shop we have following templates
-RpgSaga: 
-- [Python](https://gitlab.akvelon.net:9443/bootcamp/rpgsagapython)
-- [NodeJs](https://gitlab.akvelon.net:9443/bootcamp/rpgsagats)
-- [.Net](https://gitlab.akvelon.net:9443/bootcamp/rpgsaganetcore)
-
-Online Shop:
-- [.Net](https://gitlab.akvelon.net:9443/bootcamp/net-react-template)
-- [NodeJs](https://gitlab.akvelon.net:9443/bootcamp/nest-react-template)
-- [Python](https://gitlab.akvelon.net:9443/bootcamp/python-react-template)
-
-Also each issue in the project must have a comment with sign off from reviewer that task is fully done.
-
-## Good Luck!
+# How to Work with this Project
+
+This project is your Portfolio: your future interviewer will take a look at that repo and pay attention to:
+1. Repository Quality (Source Code, Branches, Commits, READMEs, etc.)
+1. Issues/Board/Milestones (how many issues/milesones were closed, tickets management quality, etc.)
+1. Merge Requests (overall MRs qualry, all MRs must be reviewed and approved, etc.)
+
+1. codewars 
+1. rpgsaga
+1. onlineshop
+
+## Good Luck!