Release 12.1.0 (#420)

* prepare next development version 12.0.1-SNAPSHOT

* Fix ref in replace views w/ `findOrAddObject()`

Fixes #402

See GitHub issue for in-depth analysis and testing results.

* Add missing dist files

* Use context to get current view name

Fixes #254

* Remove `nav.mainNavi` styles (#415)

I couldn't find any occurence or usage of the CSS class `mainNavi` in the TypeScript code of the phovea, Caleydo, or datavisyn organization, nor do know where this element would be. Hence, I would remove this code.

* Prepare github changes

* Remove circleci

* prepare release_12.1.0

Co-authored-by: Holger Stitz <[email protected]>
Co-authored-by: Champari Oltion <[email protected]>
Co-authored-by: Dominic Girardi <[email protected]>
Co-authored-by: anita-steiner <>

.github/CODEOWNERS

@@ -1 +1,2 @@
 *   @thinkh
+

.github/ISSUE_TEMPLATE/bug_report.md → .github/ISSUE_TEMPLATE/bug-report.md

@@ -1,9 +1,9 @@
 ---
-name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: 'type: bug'
-assignees: ''
+name: 🐛Bug Report
+about: Create a bug report to help us improve
+title: ""
+labels: ["type: bug"]
+assignees: ""
 
 ---
 
@@ -12,6 +12,7 @@ assignees: ''
  * Release number or git hash: 
  * Browser: 
  * Deployed / Local: 
+---
 
 ### Steps to reproduce the bug
 
@@ -30,3 +31,6 @@ assignees: ''
 ### Expected Behavior
 
 > Please provide a short description which behavior you expected from your steps
+
+Thanks for taking the time to fill out this bug report 🤗
+Make sure there aren't any open/closed issues for this topic 😃

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,17 @@
+---
+name: ✨Feature Request
+about: Request a new feature or enhancement
+title: ""
+labels: ["type: feature"]
+---
+
+## Short description
+
+Please provide a short description which summarizes the idea behind this feature request and why this is useful.
+
+## User stories
+
+* As a *user*, I want to ... so that ...
+
+
+Please make sure this feature request hasn't been already submitted by someone by looking through other open/closed issues 😃

.github/pull_request_template.md

@@ -0,0 +1,45 @@
+Closes *list issues numbers here*
+
+### Developer Checklist (Definition of Done)
+
+**Issue**
+
+- [ ] All acceptance criteria from the issue are met
+- [ ] Tested in latest Chrome/Firefox
+
+**UI/UX/Vis**
+
+- [ ] Requires UI/UX/Vis review
+  - [ ] Reviewer(s) are notified (_tag assignees_)
+  - [ ] Review has occurred (_link to notes_)
+  - [ ] Feedback is included in this PR
+  - [ ] Reviewer(s) approve of concept and design
+
+**Code**
+
+- [ ] Branch is up-to-date with the branch to be merged with, i.e., develop
+- [ ] Code is cleaned up and formatted
+- [ ] Unit tests are written (frontend/backend if applicable)
+- [ ] Integration tests are written (if applicable)
+
+**PR**
+
+- [ ] Descriptive title for this pull request is provided (will be used for release notes later)
+- [ ] Reviewer and assignees are defined
+- [ ] Add type label (e.g., *bug*, *feature*) to this pull request
+- [ ] Add release label (e.g., `release: minor`) to this PR following [semver](https://semver.org/)
+- [ ] The PR is connected to the corresponding issue (via `Closes #...`)
+- [ ] [Summary of changes](#summary-of-changes) is written
+
+
+### Summary of changes
+
+- 
+
+### Screenshots
+
+
+### Additional notes for the reviewer(s)
+
+-  
+Thanks for creating this pull request 🤗

.github/workflows/build.yml

@@ -0,0 +1,8 @@
+name: build
+
+on: [push, workflow_dispatch]
+
+jobs:
+  build:
+    uses: datavisyn/github-workflows/.github/workflows/build-node.yml@main
+    secrets: inherit 

.github/workflows/publish.yml

@@ -0,0 +1,8 @@
+name: publish
+
+on: workflow_dispatch
+
+jobs:
+  publish:
+    uses: datavisyn/github-workflows/.github/workflows/publish-node.yml@main
+    secrets: inherit       

.github/workflows/release.yml

@@ -0,0 +1,8 @@
+name: release
+
+on: workflow_dispatch
+
+jobs:
+  release:
+    uses: datavisyn/github-workflows/.github/workflows/release-source.yml@main
+    secrets: inherit