Skip to content

Add Solace PubSub+ instructions for Copilot - #1

Open
sumitkc wants to merge 1 commit into
lalrow:mainfrom
sumitkc:add-solace-instructions
Open

Add Solace PubSub+ instructions for Copilot#1
sumitkc wants to merge 1 commit into
lalrow:mainfrom
sumitkc:add-solace-instructions

Conversation

@sumitkc

@sumitkc sumitkc commented Apr 29, 2026

Copy link
Copy Markdown

Summary

  • Adds .github/instructions/solace.instructions.md so Copilot applies the team's Solace messaging conventions when editing Java code.
  • Covers library choice (solace-spring-boot-starter), config (no hardcoded broker URLs), topic naming (<domain>/<bounded-context>/<version>/<event>), QoS (Persistent vs Direct), producer/consumer shape, DMQ handling, reconnection, logging/observability, and testing (Testcontainers for integration).
  • Mirrors the format of the existing spring-boot.instructions.md (numbered sections, applyTo frontmatter, terse rule-style prose).

Test plan

  • Confirm applyTo: "**/src/main/**/*.java" is the desired scope (could be narrowed to **/*Publisher*.java/**/*Subscriber*.java if preferred).
  • Review wording/opinion of each section against the team's actual Solace setup — adjust topic-naming examples or QoS defaults if they diverge.
  • Verify the file renders correctly in Copilot's instructions picker.

🤖 Generated with Claude Code

Adds .github/instructions/solace.instructions.md so Copilot applies the
team's Solace messaging conventions (library choice, topic naming, QoS,
producer/consumer shape, DMQ handling, testing) when editing Java code.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.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.

1 participant