Initial release

.editorconfig

@@ -0,0 +1,118 @@
+# http://EditorConfig.org
+# https://gds-way.cloudapps.digital/manuals/programming-languages/editorconfig
+root = true
+
+[*.java]
+indent_size = 4
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = false
+continuation_indent_size = 8
+
+[*.scss]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.erb]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.html]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.njk]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.css]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.js]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.json]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.py]
+indent_size = 4
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+max_line_length = 119
+
+[*.rb]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.sh]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.yml]
+indent_size = 2
+indent_style = space
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[Makefile]
+indent_size = 2
+indent_style = tab
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[**vendor**]
+indent_size =
+indent_style =
+charset =
+end_of_line =
+insert_final_newline =
+trim_trailing_whitespace =
+max_line_length =

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,48 @@
+---
+name: Bug report
+about: Report a bug to help us improve the project
+
+---
+
+<!--
+
+Have you read the Code of Conduct? By filing an Issue, you are expected to comply with it, including treating everyone with respect:
+
+https://github.com/whatterz/nhsuk-visual-studio-code-extension/blob/master/CODE_OF_CONDUCT.md
+
+Do you want to ask a question? Are you looking for support? You can email [support@humanedesign.co](support@humanedesign.co) putting the repository name in the subject line.
+
+-->
+
+### Prerequisites
+
+* [ ] Put an X between the brackets on this line if you have done all of the following:
+    * Reproduced the problem
+    * Followed all applicable steps in the debugging guide
+    * Checked the FAQs on the message board for common solutions
+    * Checked that your issue doesn't exist: https://github.com/whatterz/nhsuk-visual-studio-code-extension/issues
+    * Checked that there is not already a package that provides the described functionality
+
+### Description
+
+[Description of the issue]
+
+### Steps to Reproduce
+
+1. [First Step]
+2. [Second Step]
+3. [and so on...]
+
+**Expected behaviour:** [What you expect to happen]
+
+**Actual behaviour:** [What happens]
+
+**Reproduces how often:** [What percentage of the time does it reproduce?]
+
+### Versions
+
+You can get this information from the CHANGELOG. Also, please include details of the browser and OS version you're running.
+
+### Additional Information
+
+Provide any additional information, configuration or data that might be necessary to reproduce the issue.

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,43 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+<!--
+
+Have you read the Code of Conduct? By filing an Issue, you are expected to comply with it, including treating everyone with respect:
+
+https://github.com/whatterz/nhsuk-visual-studio-code-extension/blob/master/CODE_OF_CONDUCT.md
+
+Do you want to ask a question? Are you looking for support? You can email [support@humanedesign.co](support@humanedesign.co) putting the repository name in the subject line.
+
+---
+
+Keep in mind that this code is customisable. Please consider the following options before filing this issue:
+
+* Tweak the project's configuration, styles, etcetera.
+* Install a community package.
+* Create a package or enhance an existing package.
+
+If none of these options is appropriate for the feature you want, please explain why that's the case by filling out the issue template below.
+
+Also, note that the team has finite resources, so it's unlikely that we'll work on feature requests. If we're interested in a particular feature, however, we'll follow up and ask you to submit an RFC to talk about it in more detail.
+
+-->
+
+## Summary
+
+Provide a one-paragraph explanation of the feature you are requesting.
+
+## Motivation
+
+Why are we doing this? What use cases does it support? What is the expected outcome?
+
+## Describe alternatives you've considered
+
+Include a clear and concise description of the alternative solutions you've considered. Make sure you explain why existing functionality isn't suitable for this feature.
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE/BUG_FIX.md

@@ -0,0 +1,57 @@
+### Requirements for contributing a bug fix
+
+* Fill out the template below. Maintainers are free to close any pull requests that do not include enough information, at their discretion.
+* The pull request must only fix an existing bug. To contribute other changes, you must use a different template. You can see all templates at https://github.com/whatterz/nhsuk-visual-studio-code-extension/tree/master/.github/PULL_REQUEST_TEMPLATE.
+* The pull request must update the test suite to demonstrate the changed functionality.
+* After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see https://github.com/whatterz/nhsuk-visual-studio-code-extension/tree/master/CONTRIBUTING.md#pull-requests.
+
+### Identify the bug
+
+<!--
+
+Link to the issue describing the bug that you're fixing.
+
+If there is not yet an issue for your bug, please open a new issue and then link to that issue in your pull request.
+Note: In some cases, one person's "bug" is another person's "feature." If the pull request does not address an existing issue with the "bug" label, the maintainers have the final say on whether the current behaviour is a bug.
+
+-->
+
+### Description of the change
+
+<!--
+
+We must be able to understand the design of your change from this description. The pull request may be closed at the maintainers' discretion if we can't get a good idea of what the code does from the description provided. 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.
+
+-->
+
+### Alternative designs
+
+<!-- Explain what other alternates you considered and why the proposed version was selected -->
+
+### Possible drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Verification process
+
+<!--
+
+What process did you follow to verify that the change has not introduced any regressions? Describe the actions you performed (including buttons you clicked, text you typed, commands you ran, etcetera), and describe the results you observed.
+
+-->
+
+### Release notes
+
+<!--
+
+Please describe the changes in a single line that explains this improvement in terms that a user can understand. This text forms part of the release notes.
+
+If this change is not user-facing or notable enough to for release notes, you may use the strings "Not applicable" or "N/A" here.
+
+Examples:
+
+- The GitHub package now allows you to add co-authors to commits.
+- Fixed an issue where multiple cursors did not work in a file with a single line.
+- Increased the performance of searching and replacing across a whole project.
+
+-->

.github/PULL_REQUEST_TEMPLATE/DOCUMENTATION.md

@@ -0,0 +1,28 @@
+### Requirements for contributing to documentation
+
+* Fill out the template below. Maintainers are free to close any pull requests that do not include enough information, at their discretion.
+* The pull request must only contribute documentation (for example, markdown files or API docs). To contribute other changes, you must use a different template. You can see all templates at https://github.com/whatterz/nhsuk-visual-studio-code-extension/tree/master/.github/PULL_REQUEST_TEMPLATE.
+
+### Description of the change
+
+<!--
+
+We must be able to understand the purpose of your change from this description. The pull request may be closed at the maintainers' discretion if we can't get a good idea of the benefits of the change from the description provided.
+
+-->
+
+### Release notes
+
+<!--
+
+Please describe the changes in a single line that explains this improvement in terms that a user can understand. This text forms part of the release notes.
+
+If this change is not user-facing or notable enough to for release notes, you may use the strings "Not applicable" or "N/A" here.
+
+Examples:
+
+- The GitHub package now allows you to add co-authors to commits.
+- Fixed an issue where multiple cursors did not work in a file with a single line.
+- Increased the performance of searching and replacing across a whole project.
+
+-->

.github/PULL_REQUEST_TEMPLATE/FEATURE_CHANGE.md

@@ -0,0 +1,72 @@
+### Requirements for adding, changing or removing a feature
+
+* Fill out the template below. Maintainers are free to close any pull requests that do not include enough information, at their discretion.
+* The pull request must contribute a change that has been endorsed by the maintainer team. See details in the template below.
+* The pull request must update the test suite to exercise the updated functionality.
+* After you create the pull request, all status checks must pass before a maintainer reviews your contribution.
+
+### Issue or RFC endorsed by the maintainers
+
+<!--
+
+Link to the issue or RFC to which your change relates. This link must be one of the following:
+
+* An open issue with the `help-wanted` label
+* An open issue with the `triaged` label
+* An RFC with "accepted" status
+
+To contribute an enhancement that isn't covered by one of the items above, please follow our guide for suggesting an enhancement:
+
+https://github.com/whatterz/nhsuk-visual-studio-code-extension/blob/master/CONTRIBUTING.md#suggesting-enhancements
+
+To contribute other changes, you must use a different template. You can see all templates at:
+
+https://github.com/whatterz/nhsuk-visual-studio-code-extension/tree/master/.github/PULL_REQUEST_TEMPLATE.
+
+-->
+
+### Description of the change
+
+<!--
+
+We must be able to understand the design of your change from this description. The pull request may be closed at the maintainers' discretion if we can't get a good idea of what the code does from the description provided. 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.
+
+-->
+
+### Alternative designs
+
+<!-- Explain what other alternates you considered and why the proposed version was selected -->
+
+### Possible drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Verification process
+
+<!--
+
+What process did you follow to verify that your change has the desired effects?
+
+- How did you verify that all new functionality works as expected?
+- How did you verify that all changed functionality works as expected?
+- How did you verify that the change has not introduced any regressions?
+
+Describe the actions you performed (including buttons you clicked, text you typed, commands you ran, etcetera), and describe the results you observed.
+
+-->
+
+### Release notes
+
+<!--
+
+Please describe the changes in a single line that explains this improvement in terms that a user can understand. This text forms part of the release notes.
+
+If this change is not user-facing or notable enough to for release notes, you may use the strings "Not applicable" or "N/A" here.
+
+Examples:
+
+- The GitHub package now allows you to add co-authors to commits.
+- Fixed an issue where multiple cursors did not work in a file with a single line.
+- Increased the performance of searching and replacing across a whole project.
+
+-->