original code

.github/CODEOWNERS

-# Codeowners file by GitHub
-# Reference: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
-# Each line is a file pattern followed by one or more owners.
-# Order is important; the last matching pattern takes the most
-# precedence.
-
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @amundsen-io/amundsen-committerswill be requested for
-# review when someone opens a pull request.
-*       @amundsen-io/amundsen-committers
-
-/amundsen-kube-helm/ @feng-tao @jornh @javamonkey79

.github/ISSUE_TEMPLATE/bug-report.md

----
-name: Bug Report
-about: Create a bug report
-title: Bug Report
-labels: bug
-assignees: ''
-
----
-
-<!--- Provide a general summary of the issue in the Title above -->
-<!--- Look through existing open and closed issues to see if someone has reported the issue before -->
-
-## Expected Behavior
-<!--- Tell us what should happen -->
-
-## Current Behavior
-<!--- Tell us what happens instead of the expected behavior -->
-
-## Possible Solution
-<!--- Not obligatory, but suggest a fix/reason for the bug -->
-
-## Steps to Reproduce
-<!--- Provide a link to a live example, or an unambiguous set of steps to -->
-<!--- reproduce this bug. Include code to reproduce, if relevant -->
-1.
-2.
-3.
-4.
-
-## Screenshots (if appropriate)
-
-## Context
-<!--- How has this issue affected you? -->
-<!--- Providing context helps us come up with a solution that is most useful in the real world -->
-
-## Your Environment
-<!--- Include as many relevant details about the environment you experienced the bug in -->
-* Amunsen version used:
-* Data warehouse stores:
-* Deployment (k8s or native):
-* Link to your fork or repository:
\ No newline at end of file

.github/ISSUE_TEMPLATE/feature-request.md

----
-name: Feature Request
-about: Create a feature request
-title: Feature Proposal
-labels: feature proposal
-assignees: ''
-
----
-
-<!--- Provide a general summary of the feature request or improvement in the Title above -->
-<!--- Look through existing open and closed feature proposals to see if someone has asked for the feature before -->
-
-## Expected Behavior or Use Case
-<!--- Tell us how it should work -->
-
-## Service or Ingestion ETL
-<!--- Tell us to which service or component this request is related to -->
-
-## Possible Implementation
-<!--- Not obligatory, suggest ideas of how to implement the addition or change -->
-
-## Example Screenshots (if appropriate):
-
-## Context
-<!--- Why do you need this feature or improvement? What is your use case? What are you trying to accomplish? -->
-<!--- Providing context helps us come up with a solution that is most useful in the real world -->
\ No newline at end of file

.github/PULL_REQUEST_TEMPLATE.md

-<!---
-Provide a general summary of your changes in the Title above
-Include one of these prefixes:
-  fix – Fixes an unexpected problem or unintended behavior
-  feat – Adds a new feature
-  docs – A documentation improvement task
-  build – A task related to our build system
-  ci – A task related to our ci system
-  perf – A performance improvement
-  refactor – A code refactor PR
-  style – A task about styling
-  test – A PR that improve test coverage
-  chore – A regular maintenance chore or task
-  other – Any other kind of PR
-
-Example: docs: Improves the documentation on...
--->
-
-### Summary of Changes
-
-<!-- Include a summary of changes -->
-
-### Documentation
-
-<!-- What documentation did you add or modify and why? Add any relevant links -->
-
-### CheckList
-
-Make sure you have checked **all** steps below to ensure a timely review.
-
-- [ ] PR title addresses the issue accurately and concisely, including a title prefix.
-- [ ] PR includes a summary of changes.
-- [ ] My commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)"

.github/titleLint.yml

-regex: (build|ci|docs|feat|fix|perf|refactor|style|test|chore|other): .*

.github/workflows/deploy_docs.yml

-name: Publish docs via GitHub Pages
-on:
-  push:
-    branches:
-      - master
-
-jobs:
-  build:
-    name: Deploy docs
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout master
-        uses: actions/checkout@v1
-      - name: Checkout submodules using a PAT
-        run: |
-          git config --file .gitmodules --get-regexp url | while read url; do
-            git config --file=.gitmodules $(echo "$url" | sed -E "s/git@github.com:|https:\/\/github.com\//https:\/\/${{ secrets.CI_PAT }}:${{ secrets.CI_PAT }}@github.com\//")
-          done
-          git submodule sync
-          git submodule update --init --recursive
-      - name: Deploy docs
-        uses: mhausenblas/mkdocs-deploy-gh-pages@master
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}