chore: copy of existing component github folder #1

.github/CODEOWNERS

@@ -0,0 +1,11 @@
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-syntax
+
+# The Auro team will be the default owners for everything in the repo.
+*       @AlaskaAirlines/generalauroreviewers
+
+# Order is important. The last matching pattern has the most precedence.
+# If a pull request touches any files in the ./src dir, only these owners
+# will be requested to review.
+./src/*    @AlaskaAirlines/auroteamreviewers

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

.github/CONTRIBUTING.md

@@ -0,0 +1,131 @@
+# Auro Design System Contributing Guidelines
+
+Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
+
+## Feature Requests
+
+Feature requests stem from a business need. Also be sure to find out whether your idea fits with the scope and aims of the project of if this serves to address a personal/local scenario. It is up to you to make a strong case to convince the project's managers of the merits of this feature. Please provide as much detail and context as possible.
+
+## Reporting Bugs
+
+A bug is defined by: "A demonstrable problem that is caused by a file in the repository." Good bug reports are extremely helpful - thank you!
+
+Guidelines for bug reports:
+
+1. Use the search option under Boards > Work Items — check if the issue has already been reported
+1. Check if the issue has been fixed — try to reproduce it using the latest main or development branch in the repository
+1. Isolate the problem — ideally create a reduced test case and a live example
+
+A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
+
+Poor bug reports will be reassigned back to the creator for revision prior to any additional investigation.
+
+## Submitting pull requests
+
+No one other than repository managers have direct access to the repository. For all pull requests you must first fork the project to your own Github account.
+
+All new work that is to be considered for merging with the `MAIN` branch must start from a new feature branch of work. This feature branch should be in response to either a bug or a new business requirement.
+
+### Feature branch naming
+
+The name of the feature branch should be descriptive as to the nature of the work and please include any references to the story or bug work item ID.
+
+### Conventional Commits
+
+This project utilizes [Conventional Commits](https://www.conventionalcommits.org/) to auto-generate release versions, based on the [Angular Commit Message Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
+
+
+```
+<type>[optional scope]: <description>
+```
+
+All commit messages must be prefixed with a specific type so that the semver release configuration can analyze the commit and apply the correct version release. Please see the following types with their respective meanings.
+
+#### MAJOR
+
+For a MAJOR release, you MUST follow this template. The use `BREAKING CHANGE:` in conjunction with any other commit type is required in order to push a major release.
+
+```
+perf(pencil): remove graphiteWidth option
+
+BREAKING CHANGE: The graphiteWidth option has been removed.
+The default graphite width of 10mm is always used for performance reasons.
+```
+
+#### MINOR
+```
+feat(pencil): add 'graphiteWidth' option
+```
+
+#### PATCH
+```
+fix(pencil): stop graphite breaking when too much pressure applied
+```
+
+#### Other commit types
+
+| type | description |
+|---|---|
+| build | Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) |
+| ci | Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) |
+| docs | Documentation only changes |
+| feat | A new feature (this correlates with `MINOR` in semantic versioning) |
+| fix | A bug fix (this correlates with `PATCH` in semantic versioning) |
+| perf | A code change that improves performance |
+| BREAKING CHANGE | A code change that is not backwards compatible (correlating with `MAJOR` in semantic versioning) |
+| refactor | A code change that neither fixes a bug nor adds a feature |
+| style | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |
+| test | Adding missing tests or correcting existing tests  |
+
+#### Git commit messages
+
+Once you have completed your feature update, please commit all changes to the branch. All commit messages should use an **imperative mood**.
+
+Imperative mood simply means _“spoken or written as if giving a command or instruction”_. A few examples are:
+
+* Clean your room
+* Close the door
+* Take out the trash
+
+A properly formed Git commit subject line should always be able to complete the following sentence:
+
+_"If applied, this commit will (your subject line here)."_
+
+For example:
+
+* If applied, this commit will `refactor component X for accessibility`
+* If applied, this commit will `add feature Y to component X`
+
+Example messages when using Conventional Commits:
+
+```
+$ build: update to build step to include postCSS
+
+$ docs: address issue #14, typo in install instructions
+
+$ perf: restructure API to comply with new feature spec
+
+$ feat: add ability to consume large data as an array versus string
+
+$ fix: address issue #57 in regards to color output
+```
+
+### Push branch and submit pull request
+
+One you have committed new work to your feature branch, be sure to push your updates to the Github repository. Depending on your IDE or CLI configuration this may be a manual or automatic step.
+
+On the pull request page, the new pull request should be `[your-new-branch] into [main]`
+
+Please be sure to follow the **Pull Request template** that appears on the comment window.
+
+You must select up to two reviews from your team to validate that the update is correct, solves the problem presented by the story and meets all the requirements for a new merge.
+
+Finally, click the `Create` button.
+
+## Accepting and merging a pull request
+
+Once a pull request has been created, the assigned reviewers should have received notifications. Each reviewer is expected to view the pull request and review all the data per this request.
+
+A reviewer has the option to leave comments, ask questions and reject the pull request.
+
+Once two reviewers have approved the work, the pull request can then be completed.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,55 @@
+name: Bug report
+description: Create a report to help us improve
+title: '[issue summary] Please verify version before submitting new issue'
+labels:
+  - auro-cli
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: input
+    id: version
+    attributes:
+      label: Please verify the version of auro-cli you have installed
+  - type: markdown
+    attributes:
+      value: >
+        [![See it on
+        NPM!](https://img.shields.io/npm/v/@aurodesignsystem/auro-cli?style=for-the-badge&color=orange)](https://www.npmjs.com/package/@aurodesignsystem/auro-cli)
+  - type: textarea
+    id: details
+    attributes:
+      label: Please describe the bug
+      description: List out the steps to reproduce the behavior and include screenshots
+      placeholder: |
+        1. Go to '...'
+        2. Click on '....'
+        3. Scroll down to '....'
+        4. See error
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: Please add a clear and concise description of what you expected to
+        happen.
+  - type: dropdown
+    id: os
+    attributes:
+      label: What OS are you seeing the problem on?
+      multiple: true
+      options:
+        - Linux
+        - Mac
+        - Windows
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here.
+  - type: textarea
+    id: exit-criteria
+    attributes:
+      label: Exit criteria
+      description: Define your issue's exit criteria
+      placeholder: "This issue can be closed once the error has been corrected. Any additional scope e.g. updates or refactors, should be discussed PRIOR to adding scope to this issue."

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,27 @@
+name: Feature request
+description: Suggest an idea for this project
+title: 'auro-cli: [feature summary]'
+labels:
+  - auro-cli
+body:
+  - type: textarea
+    id: request
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is.
+      placeholder: Ex. I'm always frustrated when [...]
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+  - type: textarea
+    id: alternative
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/general-support.yml

@@ -0,0 +1,21 @@
+name: General support
+description: Suggestions that are not related to bugs or new features
+title: 'auro-cli: [issue]'
+labels:
+  - auro-cli
+body:
+  - type: textarea
+    id: request
+    attributes:
+      label: General Support Request
+      description: A clear and concise description of what you are interested in seeing.
+  - type: textarea
+    id: solution
+    attributes:
+      label: Possible Solution
+      description: Not obligatory, but suggest an idea of how to implement the requested update.
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+# Alaska Airlines Pull Request
+
+## Type of change:
+
+Please delete options that are not relevant.
+
+- [ ] New capability
+- [ ] Revision of an existing capability
+- [ ] Infrastructure change (automation, etc.)
+- [ ] Other (please elaborate)
+
+## Checklist:
+
+- [ ] My update follows the CONTRIBUTING guidelines of this project
+- [ ] I have performed a self-review of my own update
+
+**By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.**
+
+_Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission._
+
+**Thank you for your submission!**<br>
+-- Auro Design System Team