Initial commit

.gitattributes

@@ -0,0 +1,5 @@
+* text eol=lf
+
+# Denote all files that are truly binary and should not be modified.
+*.png binary
+*.jar binary

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# default owners for everything in the repository.
+*   @Microsoft/accessibility-insights-code-owners

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,45 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ""
+labels: bug, needs triage
+assignees: ""
+---
+
+## Describe the bug
+
+<!-- A clear and concise description of what the bug is. -->
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. See error
+
+## Expected behavior
+
+<!-- A clear and concise description of what you expected to happen. -->
+
+## Screenshots
+
+<!-- If applicable, add screenshots to help explain your problem. -->
+
+## Context (please complete the following information)
+
+- Android Version: <!--e.g. Kitkat/Oreo -->
+- Service Version & Environment: <!--e.g. 1.140.1 Insider -->
+- Target Application: <!--e.g. Android Messaging -->
+
+## Are you willing to submit a PR?
+
+<!-- If asked, will you be willing to submit a PR to fix this bug? -->
+
+## Did you search for similar existing issues?
+
+<!-- Did you search for similar issues in our github issues or on [stackoverflow](https://stackoverflow.com/questions/tagged/accessibility-insights) -->
+
+## Additional context
+
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature request
+assignees: ''
+---
+
+## Is your feature request related to a problem? Please describe.
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+## Describe the desired outcome
+<!-- A clear and concise description of what you want to happen. -->
+
+## Describe alternatives you've considered
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+## Additional context
+<!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/general_question.md

@@ -0,0 +1,16 @@
+---
+name: General Question
+about: This is a template for people to ask questions that don't fit into any other issue categories
+title: ""
+labels: question
+assignees: ""
+---
+
+**We encourage tool related questions to be asked on stackoverflow.com and tagged with `accessibility-insights`.**
+
+## Your question here
+
+<!--
+Make sure to provide enough context. If you have spoken to a team member please mention them here.
+Add any items (screenshots etc) that will help.
+-->

.github/pull_request_template.md

@@ -0,0 +1,20 @@
+#### Description of changes
+
+<!--
+  A great PR description includes:
+    * A high level overview (usually a sentence or two) describing what the PR changes
+    * What is the motivation for the change? This can be as simple as "addresses issue #123"
+    * Were there any alternative approaches you considered? What tradeoffs did you consider?
+    * What **doesn't** the change try to do? Are there any parts that you've intentionally left out-of-scope for a later PR to handle? What are the issues/work items tracking that later work?
+    * Is there any other context that reviewers should consider? For example, other related issues/PRs, or any particularly tricky/subtle bits of implementation that need closer-than-normal review?
+-->
+
+#### Pull request checklist
+
+<!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox -->
+
+- [ ] Addresses an existing issue: #0000
+- [ ] Added/updated relevant unit test(s)
+- [ ] Ran `./gradlew fastpass` from `AccessibilityInsightsForAndroidService`
+- [ ] PR title _AND_ final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`).
+- [ ] **Important:** If pull request builds don't automatically run, they may be explicitly triggered. To do so, a team member should comment `/azp run` on this PR.