Skip to content

Chore: [AEA-0000] - workflow to sync copilot instructions#62

Open
anthony-nhs wants to merge 15 commits intomainfrom
copilot
Open

Chore: [AEA-0000] - workflow to sync copilot instructions#62
anthony-nhs wants to merge 15 commits intomainfrom
copilot

Conversation

@anthony-nhs
Copy link
Contributor

@anthony-nhs anthony-nhs commented Feb 11, 2026

Summary

  • Routine Change

Details

  • workflow to sync copilot instructions
  • add copilot instructions to sync to each repo

@github-actions
Copy link
Contributor

This PR is linked to a ticket in an NHS Digital JIRA Project. Here's a handy link to the ticket:

AEA-0000

@sonarqubecloud
Copy link

@anthony-nhs anthony-nhs enabled auto-merge (squash) February 24, 2026 09:45
@@ -0,0 +1,109 @@
# Copilot instructions for CloudFormation YAML in this repo
---
description: 'Brief description of the instruction purpose and scope'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: probably should say something like: Guidelines for writing, reviewing, and maintaining AWS resource orchestration with cloudformation

# Java Copilot Instructions for NHS FHIR Validator Lambda

---
description: 'Brief description of the instruction purpose and scope'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: again should probably say something more comprehensive here

# Copilot Instructions for Kotlin Files

---
description: 'Brief description of the instruction purpose and scope'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: and here

Comment on lines +207 to +222
## General Instructions

- High-level guideline 1
- High-level guideline 2

## Best Practices

- Specific practice 1
- Specific practice 2

## Code Standards

### Naming Conventions
- Rule 1
- Rule 2

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these can prolly get removed due to the language specific instructions

Comment on lines +223 to +225
### File Organization
- Structure 1
- Structure 2

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

potentially this too, i feel like we got a general file organisation structure for higher level projects but individual packages i reckon still somewhat fluctuate, so those would probably need to go in the language specific instructions

Comment on lines +229 to +245
### Pattern 1
Description and example

\`\`\`language
code example
\`\`\`

### Pattern 2
Description and example

## Validation

- Build command: `command to verify`
- Linting: `command to lint`
- Testing: `command to test`
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removable

Comment on lines +62 to +78
### 3. Examples and Code Snippets

Provide concrete examples with clear labels:

```markdown
### Good Example
\`\`\`language
// Recommended approach
code example here
\`\`\`

### Bad Example
\`\`\`language
// Avoid this pattern
code example here
\`\`\`
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deletable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants