Rossbugginsnhs/2025 10/23/copilot instructions 001 (#83)

* hook excludes.

* hook excludes.

* copilot instructions.

Author: RossBugginsNHS

.devcontainer/nhs-notify-devcontainer-loaded/devcontainer.json

@@ -0,0 +1,12 @@
+{
+  "containerEnv": {
+    "GITHUBMONITOR": "false",
+    "MAKECONFIG": "false",
+    "SHOWWELCOME": "true",
+    "UPDATEFROMTEMPLATE": "false"
+  },
+  "image": "ghcr.io/nhsdigital/nhs-notify-devcontainer-loaded:1.0.5",
+  "name": "Notify Loaded Dev Container 1.0.5",
+  "postCreateCommand": "echo My own container created",
+  "postStartCommand": "echo My own container started"
+}

.devcontainer/devcontainer.json .devcontainer/old/devcontainer.json.devcontainer/devcontainer.json renamed to .devcontainer/old/devcontainer.json

@@ -0,0 +1,17 @@
+# NHS Notify Digital Letters
+
+Our core programming language is typescript, but also Python.
+
+Our docs are in [.docs](./docs) and are built with jekyll.
+
+This repository is for handling pre rendered letters, handling them for print and also making available for digital viewing. If viewed digitally, then they won't be printed.
+
+This is just one sub domain of the whole of NHS Notify. Inside of this subdomain, there are a number of services, each with a number of microservices. The service could be a bounded context with separate deployability.
+
+Services communicate in an event driven manner, using cloud events. Digital letters has its own Event Bridge, and any events to share with the wider NHS Notify system are forwarded to the core Event Bridge.
+
+You can build docs with `make build` in [.docs](./docs), you will need to `make install` first. This will output to [.docs/_site](./docs/_site). Once this is built you can find out about our architecture at [./docs/site/architecture/c4/index.html](./docs/site/architecture/c4/index.html). It is event driven, events can all be found at [./docs/_site/events.html](./docs/_site/events.html)
+
+All of our events will have their schemas stored in [./schemas/events](./schemas/events). These schemas are used for validation and code generation. The schemas are written in yaml and follow the json schema spec. You can find out more about json schema at [https://json-schema.org/](https://json-schema.org/).
+
+For each event, there will be a schema for the envelope (this is cloud events, and will reference the default NHS Notify cloudevent profile schema). And there will also be a schema for the data payload. The data payload schema will be referenced in the envelope schema.

.github/copilot-instructions.md

@@ -106,7 +106,11 @@
       "editor.defaultFormatter": "esbenp.prettier-vscode"
     },
     "window.title": "${separator}${activeRepositoryName}${separator}${activeRepositoryBranchName}${separator}[${remoteName}]",
-    "window.titleSeparator": " : "
+    "window.titleSeparator": " : ",
+    "chat.instructionsFilesLocations": {
+      ".github": true,
+      ".github/instructions": true
+    }
   },
   "extensions": {
     "recommendations": [

project.code-workspace

@@ -1,6 +1,7 @@
 [A-Z]+s
 Bitwarden
 bot
+cloudevent
 Cognito
 Cyber
 Dependabot
@@ -14,16 +15,19 @@ Git[Hh]ub
 Gitleaks
 Grype
 idempotence
+jekyll
 Jira
 Makefile
 OAuth
 Octokit
 onboarding
 Podman
+pre
 Python
 rawContent
 sed
 Syft
 Terraform
 toolchain
 Trufflehog
+yaml

scripts/config/vale/styles/config/vocabularies/words/accept.txt

@@ -40,6 +40,7 @@ EXCLUDED_DIRS=(
   ".venv/"
   "docs/"
   "node_modules/"
+  ".devcontainer/"
 )