Merge branch 'master' into ui/delete-branch

Author: StanleyGoldman

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,32 @@
+<!--
+
+Have you read GitHub for Unity's Code of Conduct? By filing an Issue, you are expected to comply with it, including treating everyone with respect: https://github.com/github-for-unity/Unity/blob/master/CODE_OF_CONDUCT.md
+
+-->
+
+### Prerequisites
+
+- Be sure to run with tracing enabled to capture runtime details in the log file
+- Include the log file in the PR.
+  - On Windows, the extension log file is at `%LOCALAPPDATA%\GitHubUnity\github-unity.log`
+  - On macOS, the extension log file is at `~/.local/share/GitHubUnity/github-unity.log`
+
+### Description
+
+<!-- Description of the issue -->
+
+### Steps to Reproduce
+
+1. [First Step]
+2. [Second Step]
+3. [and so on...]
+
+**Expected behavior:** [What you expect to happen]
+
+**Actual behavior:** [What actually happens]
+
+**Reproduces how often:** [What percentage of the time does it reproduce?]
+
+### Additional Information
+
+Any additional information, configuration or data that might be necessary to reproduce the issue.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+### Requirements
+
+* Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
+* All new code requires tests to ensure against regressions
+
+### Description of the Change
+
+<!--
+
+We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
+
+-->
+
+### Alternate Designs
+
+<!-- Explain what other alternates were considered and why the proposed version was selected -->
+
+### Benefits
+
+<!-- What benefits will be realized by the code change? -->
+
+### Possible Drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Applicable Issues
+
+<!-- Enter any applicable Issues here -->

.gitignore

@@ -1,7 +1,9 @@
 .vs/
+.idea/
 packages/
 _NCrunch_GitHub.Unity
 *.user
 .DS_Store
 build/
-TestResult.xml
+TestResult.xml
+submodules/

.gitmodules

@@ -1,9 +1,3 @@
 [submodule "script"]
 	path = script
 	url = [email protected]:github-for-unity/UnityBuildScripts
-[submodule "submodules/octokit.net"]
-	path = submodules/octokit.net
-	url = https://github.com/editor-tools/octokit.net.git
-[submodule "submodules/dotnet-httpclient35"]
-	path = submodules/dotnet-httpclient35
-	url = https://github.com/shana/dotnet-httpClient35

CONTRIBUTING.md

@@ -0,0 +1,178 @@
+# Contributing to GitHub for Unity
+
+:+1: :tada: :sparkling_heart: Thanks for your interest! :sparkling_heart: :tada: :+1:
+
+The following is a set of guidelines for contributing to GitHub for Unity and its
+related projects, which are hosted in the [GitHub for Unity Organization](https://github.com/github-for-unity)
+on GitHub. These are just guidelines, not rules. Use your best judgment, and
+feel free to propose changes to this document in a pull request.
+
+Note that GitHub for Unity is currently a public alpha, so everything is likely to
+change over time as we learn and refine how we work with the community.
+
+#### Table Of Contents
+
+[What should I know before I get started?](#what-should-i-know-before-i-get-started)
+  * [Code of Conduct](#code-of-conduct)
+  * [The Roadmap](#the-roadmap)
+
+[How Can I Contribute?](#how-can-i-contribute)
+  * [How to Build](#how-to-build)
+  * [Reporting Bugs](#reporting-bugs)
+  * [Suggesting Enhancements](#suggesting-enhancements)
+  * [Up for Grabs](#up-for-grabs)
+
+[Additional Notes](#additional-notes)
+  * [Issue and Pull Request Labels](#issue-and-pull-request-labels)
+
+## What should I know before I get started?
+
+### Code of Conduct
+
+This project adheres to the Contributor Covenant [code of conduct](CODE_OF_CONDUCT.md).
+By participating, you are expected to uphold this code.
+Please report unacceptable behavior to [[email protected]](mailto:[email protected]).
+
+### The Roadmap
+
+Currently GitHub for Unity is in a public alpha, and the team is focused on
+triaging reported issues and working towards a 1.0 milestone.
+You can follow this progress under the [Milestones](https://github.com/github-for-unity/Unity/milestones)
+tab.
+
+We're still thinking about where we want to take GitHub for Unity after we reach
+this 1.0 milestone. If you have ideas or suggestions please read the [Suggesting Enhancements](#suggesting-enhancements)
+section below to understand how to contribute your feedback.
+
+## How Can I Contribute?
+
+### How to Build
+
+This repository is LFS-enabled. To clone it, you should use a git client that supports git LFS 2.x and submodules.
+
+Please read the [How to Build](https://raw.githubusercontent.com/github-for-unity/Unity/master/docs/contributing/how-to-build.md) document for information on how to build GitHub for Unity.
+
+### Reporting Bugs
+
+This section guides you through submitting a bug report for GitHub for Unity.
+Following these guidelines helps maintainers and the community understand your
+report :pencil:, reproduce the behavior :computer: :computer:, and find related
+reports :mag_right:.
+
+Before creating bug reports, please check [this list](#before-submitting-a-bug-report)
+as you might find out that you don't need to create one. When you are creating
+a bug report, please [include as many details as possible](#how-do-i-submit-a-good-bug-report).
+Fill out [the required template](./.github/ISSUE_TEMPLATE.md), the information
+it asks for helps us resolve issues faster.
+
+#### Before Submitting A Bug Report
+
+**Perform a [cursory search](https://github.com/github-for-unity/Unity/labels/bug)**
+to see if the problem has already been reported. If it does exist, add a
+[reaction](https://help.github.com/articles/about-discussions-in-issues-and-pull-requests/#reacting-to-ideas-in-issues-and-pull-requests)
+to the issue to indicate this is also an issue for you, and add a
+comment to the existing issue if there is extra information you can contribute.
+
+#### How Do I Submit A (Good) Bug Report?
+
+Bugs are tracked as [GitHub issues](https://guides.github.com/features/issues/).
+
+Simply create an issue on the [GitHub for Unity issue tracker](https://github.com/github-for-unity/Unity/issues)
+and fill out the provided [issue template](./.github/ISSUE_TEMPLATE.md).
+
+The information we are interested in includes:
+
+ - details about your environment - which build, which operating system
+ - details about reproducing the issue - what steps to take, what happens, how
+   often it happens
+ - other relevant information - log files, screenshots, etc.
+
+### Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion for
+GitHub for Unity, including completely new features and minor improvements to
+existing functionality. Following these guidelines helps maintainers and the
+community understand your suggestion :pencil: and find related suggestions
+:mag_right:.
+
+Before creating enhancement suggestions, please check [this list](#before-submitting-an-enhancement-suggestion)
+as you might find out that you don't need to create one. When you are creating
+an enhancement suggestion, please [include as many details as possible](#how-do-i-submit-a-good-enhancement-suggestion).
+Fill in [the template](./.github/ISSUE_TEMPLATE.md), including the steps
+that you imagine you would take if the feature you're requesting existed.
+
+#### Before Submitting An Enhancement Suggestion
+
+**Perform a [cursory search](https://github.com/github-for-unity/Unity/labels/enhancement)**
+to see if the enhancement has already been suggested. If it has, add a
+:thumbsup: to indicate your interest in it, or comment if there is additional
+information you would like to add.
+
+#### How Do I Submit A (Good) Enhancement Suggestion?
+
+Enhancement suggestions are tracked as [GitHub issues](https://guides.github.com/features/issues/).
+
+Simply create an issue on the [GitHub for Unity issue tracker](https://github.com/github-for-unity/Unity/issues)
+and provide the following information:
+
+* **Use a clear and descriptive title** for the issue to identify the
+  suggestion.
+* **Provide a step-by-step description of the suggested enhancement** in as
+  much detail as possible. This additional context helps the maintainers to
+  understand the enhancement from your perspective
+* **Explain why this enhancement would be useful** to GitHub for Unity users.
+* **Include screenshots and animated GIFs** if relevant to help you demonstrate
+  the steps or point out the part of GitHub for Unity which the suggestion is
+  related to. You can use [this tool](http://www.cockos.com/licecap/) to record
+  GIFs on macOS and Windows.
+* **List some other applications where this enhancement exists, if applicable.**
+
+### Up For Grabs
+
+As the team is working towards the 1.0 release, we'll identify enhancements or
+bugs that can be categorized as tasks that:
+
+ - have low impact, or have a known workaround
+ - should be fixed
+ - have a narrow scope and/or easy reproduction steps
+ - can be worked on independent of other tasks
+
+These issues will be labelled as [`up-for-grabs`](https://github.com/github-for-unity/Unity/labels/up-for-grabs)
+in the repository. If you are interested in contributing to the project, please
+comment on the issue to let the maintainers (and community) know you are
+interested in picking this up.
+
+## Additional Notes
+
+### Issue and Pull Request Labels
+
+This section lists the labels we use to help us track and manage issues and
+pull requests.
+
+#### Type of Issue and Issue State
+
+| Label name | :mag_right: | Description |
+| --- | --- | --- |
+| `enhancement` | [search](https://github.com/github-for-unity/Unity/labels/enhancement) | Feature requests. |
+| `bug` | [search](https://github.com/github-for-unity/Unity/labels/bug)  | Confirmed bugs or reports that are very likely to be bugs. |
+| `question` | [search](https://github.com/github-for-unity/Unity/labels/question)  | Questions more than bug reports or feature requests (e.g. how do I do X). |
+| `more-information-needed` | [search](https://github.com/github-for-unity/Unity/labels/more-information-needed) | More information needs to be collected about these problems or feature requests (e.g. steps to reproduce). |
+| `needs-reproduction` | [search](https://github.com/github-for-unity/Unity/labels/needs-reproduction)  | Likely bugs, but haven't been reliably reproduced. |
+| `macOS` | [search](https://github.com/github-for-unity/Unity/labels/macOS)  | Issues specific to macOS users. |
+| `Windows` | [search](https://github.com/github-for-unity/Unity/labels/Windows)  | Issues specific to Windows users. |
+| `Linux` | [search](https://github.com/github-for-unity/Unity/labels/Linux)  | Issues specific to Linux users. |
+
+#### Topics
+
+| Label name | :mag_right: | Description |
+| --- | --- | --- |
+| `up-for-grabs` | [search](https://github.com/github-for-unity/Unity/labels/up-for-grabs)  | Issues marked as ideal for external contributors. |
+| `polish` | [search](https://github.com/github-for-unity/Unity/labels/polish) | Issues not critical to the application but would provide a better experience if resolved. |
+| `tech-debt` | [search](https://github.com/github-for-unity/Unity/labels/tech-debt) | Issues related to code or architecture decisions. |
+| `design` | [search](https://github.com/github-for-unity/Unity/labels/design)  | Issues that require some design input from the maintainers as part of completing the work. |
+
+#### Workflow
+
+| Label name | :mag_right: | Description |
+| --- | --- | --- |
+| `ready-for-review` | [search](https://github.com/github-for-unity/Unity/labels/ready-for-review)  | Pull Requests that are ready to be reviewed by the maintainers. |