Initial commit

.babelrc

@@ -0,0 +1,5 @@
+{
+    "presets": [
+        "es2015"
+    ]
+}

.eslintrc.json

@@ -0,0 +1,23 @@
+{
+    "env": {
+        "browser": false,
+        "commonjs": true,
+        "es6": true,
+        "node": true
+    },
+    "parserOptions": {
+        "ecmaFeatures": {
+            "jsx": true
+        },
+        "sourceType": "module"
+    },
+    "rules": {
+        "no-const-assign": "warn",
+        "no-this-before-super": "warn",
+        "no-undef": "warn",
+        "no-unreachable": "warn",
+        "no-unused-vars": "warn",
+        "constructor-super": "warn",
+        "valid-typeof": "warn"
+    }
+}

.github/CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via an issue, email, or any other method with the owners of this repository before making a change.
+
+::Please note we have a Code of Conduct, please follow it in all your interactions with the project.::
+
+## Pull Request Process
+
+1. Update the `README.md` with details of changes to the interface, this includes new environment variables, useful file locations and container parameters.
+2. Increase the version numbers in any examples files and the `README.md` to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](https://semver.org).
+
+## 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, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+### Our Standards
+
+Examples of behaviour 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 behaviour by participants include:
+
+* The use of sexualised 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 behaviour and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behaviour.
+
+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 behaviours 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 behaviour may be reported by contacting the project team at `support[at]pycom.io` and adding the `[CoC]` tag to the subject line. 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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,33 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+(Hi! 👋  Thanks for reporting an issue! Please make sure you click the link above to view the issue guidelines, then fill out the blanks below.)
+
+## What are the steps to reproduce this issue?
+1.
+2.
+3.
+
+## What happens?
+
+
+## What were you expecting to happen?
+
+
+## Any logs, error output, etc?
+*(If it’s long, please paste to https://gist.github.com and insert the link here)*
+
+
+## Any other comments?
+
+
+## What versions of software are you using?
+
+**Operating system:**
+
+**VSCode version:**
+
+**Pico-Go version:**

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+# Feature Request 🚀
+
+## Is your feature request related to a problem? Please describe.
+*A clear and concise description of what the problem is. E.g. I have an issue when...*
+
+
+## Describe the solution you'd like
+*A clear and concise description of what you want to happen. Add any considered drawbacks.*
+
+
+## Describe alternatives you've considered
+*A clear and concise description of any alternative solutions or features you've considered.*
+
+
+## Teachability, Documentation, Adoption, Migration Strategy
+*If you can, explain how users will be able to use this and possibly write out a version the docs. Maybe a screenshot or design?*

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+(Hi! 👋 Thanks for sending a pull request! Please make sure you click the link above to view the contribution guidelines, then fill out the blanks below.)
+
+## What does this implement/fix? Explain your changes.
+
+
+## Does this close any currently open issues?
+
+
+## Any relevant logs, error output, etc?
+*(If it’s long, please paste to https://gist.github.com and insert the link here)*
+
+
+## Any other comments?
+
+
+## Where has this been tested?
+
+**Operating system:**
+
+**VSCode version:**
+
+**Pico-Go version:**

.github/actions/fetch-electron-versions/action.yml

@@ -0,0 +1,17 @@
+name: "Fetch Electron Versions"
+description: "Fetch and Parse Electron Versions to Test for VSCode"
+author: BradenM
+inputs:
+  max-count:
+    default: 2
+    description: "Max Number of versions to return"
+    required: false
+  git-token:
+    description: "Github Authentication Token"
+    required: true
+outputs:
+  versions:
+    description: "Electron Versions to Test"
+runs:
+  using: "node12"
+  main: "dist/index.js"