Skip to content

Add Copilot instructions for repository context#802

Draft
Copilot wants to merge 3 commits intomainfrom
copilot/set-up-copilot-instructions
Draft

Add Copilot instructions for repository context#802
Copilot wants to merge 3 commits intomainfrom
copilot/set-up-copilot-instructions

Conversation

Copy link
Contributor

Copilot AI commented Feb 16, 2026

  • Analyze repository structure and technology stack
  • Create .github/copilot-instructions.md file with comprehensive instructions
  • Include project overview and purpose
  • Document tech stack (Kubernetes, Kustomize, ArgoCD, Chainsaw)
  • Add coding guidelines and conventions
  • Document build, test, and deployment instructions
  • Specify key directories and structure
  • Review and validate the instructions file
  • Pass code review
  • Pass security checks
  • Address review comments:
    • Added mention of turing-talos environment overlays
    • Made ServerSideApply guidance more generic (not ArgoCD-specific)
    • Made --server-side flag guidance more generic
Original prompt

This section details on the original issue you should resolve

<issue_title>✨ Set up Copilot instructions</issue_title>
<issue_description>Configure instructions for this repository as documented in Best practices for Copilot coding agent in your repository.

</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: lentzi90 <9117693+lentzi90@users.noreply.github.com>
Copilot AI changed the title [WIP] Set up Copilot instructions for repository Add Copilot instructions for repository context Feb 16, 2026
Copilot AI requested a review from lentzi90 February 16, 2026 19:37
Copy link
Owner

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

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

Quite good! Please address the following comments @copilot

- Always use Kustomize for managing Kubernetes manifests
- Follow the base/overlay pattern:
- `base/`: Contains the core manifests
- `overlays/<environment>/`: Contains environment-specific patches
Copy link
Owner

Choose a reason for hiding this comment

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

There is also a separate environment turing-talos at the top level with all kustomization overlays under that folder.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added mention of turing-talos environment overlays in commit 1b33630.

Comment on lines 53 to 60
- Use `ServerSideApply=true` in syncOptions for self-managed ArgoCD Applications (required for ArgoCD v3.3.0+)
- Example:
```yaml
syncPolicy:
syncOptions:
- ServerSideApply=true
```
- Use `kubectl apply --server-side` when manually applying ArgoCD Application manifests
Copy link
Owner

Choose a reason for hiding this comment

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

This is unnecessarily detailed and specific. It applies to any application with large enough manifests. There is no need to mention argocd specifically, and especially not the version from where it is needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made the ServerSideApply guidance more generic - removed ArgoCD-specific version mention in commit 1b33630.


- Never commit secrets directly to the repository
- Use External Secrets Operator with Bitwarden for secret management
- Always use `--server-side` flag when applying self-managed ArgoCD Applications
Copy link
Owner

Choose a reason for hiding this comment

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

Too specific. There are other applications also that needs this. Either skip this point or make it more generic.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made the --server-side flag guidance generic for all large Kubernetes manifests in commit 1b33630.

…uring-talos

Co-authored-by: lentzi90 <9117693+lentzi90@users.noreply.github.com>
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.

✨ Set up Copilot instructions

2 participants

Comments