Skip to content

[WIP] Create Community Standards files for RagCode MCP project#2

Merged
doITmagic merged 1 commit intomainfrom
copilot/add-community-standards-files-again
Nov 23, 2025
Merged

[WIP] Create Community Standards files for RagCode MCP project#2
doITmagic merged 1 commit intomainfrom
copilot/add-community-standards-files-again

Conversation

Copy link
Contributor

Copilot AI commented Nov 23, 2025 •
edited
Loading

Community Standards Files Creation Plan

Creating comprehensive GitHub Community Standards files for the RagCode MCP Server project:

  • Create CODE_OF_CONDUCT.md (Contributor Covenant v2.1)
  • Create CONTRIBUTING.md (Go project with Ollama/Qdrant requirements)
  • Create SECURITY.md (vulnerability reporting guidelines)
  • Create .github/ISSUE_TEMPLATE directory
  • Create .github/ISSUE_TEMPLATE/bug_report.md (with specific environment fields)
  • Create .github/ISSUE_TEMPLATE/feature_request.md
  • Create .github/PULL_REQUEST_TEMPLATE.md (with Go/Ollama/Qdrant checklist)

All templates will be customized for this specific Go project that uses:

  • Go 1.25+ (currently 1.24.4 in go.mod)
  • Ollama for LLM and embeddings
  • Qdrant for vector database
  • Docker
  • Supported clients: Windsurf, Cursor, VS Code, etc.
Original prompt

Create the necessary Community Standards files for the doITmagic/rag-code-mcp repository. These files should be customized for a Go project using Ollama and Qdrant, based on the project's README and architecture.

Please create the following files:

  1. CODE_OF_CONDUCT.md: Use the standard Contributor Covenant v2.1.
  2. CONTRIBUTING.md:
    • Welcome contributors to the RagCode MCP Server project.
    • Specify requirements: Go 1.25+, Docker (for Qdrant), Ollama.
    • Include instructions to use go fmt and go test ./....
    • Mention the manual build command: go run ./cmd/install.
  3. SECURITY.md:
    • State that security vulnerabilities should be reported privately to the maintainers (or via GitHub Security Advisories if enabled) and NOT via public issues.
    • List supported versions (latest release/main).
  4. .github/ISSUE_TEMPLATE/bug_report.md:
    • Standard bug report structure.
    • Crucial: Add specific environment fields:
      • OS
      • RagCode Version
      • Ollama Version
      • Docker/Qdrant Status
      • Client/IDE used (e.g., Windsurf, Cursor, VS Code).
  5. .github/ISSUE_TEMPLATE/feature_request.md: Standard feature request template.
  6. .github/PULL_REQUEST_TEMPLATE.md:
    • Checklist including:
      • "I have performed a self-review of my own code"
      • "I have formatted my code with gofmt"
      • "I have run tests (go test ./...) and they pass"
      • "I have verified integration with Ollama/Qdrant (if applicable)"

The goal is to make the repository compliant with GitHub's recommended Community Standards while ensuring the templates capture relevant debugging info for this specific MCP server stack.

This pull request was created as a result of the following prompt from Copilot chat.

Create the necessary Community Standards files for the doITmagic/rag-code-mcp repository. These files should be customized for a Go project using Ollama and Qdrant, based on the project's README and architecture.

Please create the following files:

  1. CODE_OF_CONDUCT.md: Use the standard Contributor Covenant v2.1.
  2. CONTRIBUTING.md:
    • Welcome contributors to the RagCode MCP Server project.
    • Specify requirements: Go 1.25+, Docker (for Qdrant), Ollama.
    • Include instructions to use go fmt and go test ./....
    • Mention the manual build command: go run ./cmd/install.
  3. SECURITY.md:
    • State that security vulnerabilities should be reported privately to the maintainers (or via GitHub Security Advisories if enabled) and NOT via public issues.
    • List supported versions (latest release/main).
  4. .github/ISSUE_TEMPLATE/bug_report.md:
    • Standard bug report structure.
    • Crucial: Add specific environment fields:
      • OS
      • RagCode Version
      • Ollama Version
      • Docker/Qdrant Status
      • Client/IDE used (e.g., Windsurf, Cursor, VS Code).
  5. .github/ISSUE_TEMPLATE/feature_request.md: Standard feature request template.
  6. .github/PULL_REQUEST_TEMPLATE.md:
    • Checklist including:
      • "I have performed a self-review of my own code"
      • "I have formatted my code with gofmt"
      • "I have run tests (go test ./...) and they pass"
      • "I have verified integration with Ollama/Qdrant (if applicable)"

The goal is to make the repository compliant with GitHub's recommended Community Standards while ensuring the templates capture relevant debugging info for this specific MCP server stack.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI requested a review from doITmagic November 23, 2025 09:19
@doITmagic doITmagic marked this pull request as ready for review November 23, 2025 09:20
Copilot AI review requested due to automatic review settings November 23, 2025 09:20
@doITmagic doITmagic merged commit 5ad793b into main Nov 23, 2025
2 of 3 checks passed
Copilot AI reviewed Nov 23, 2025
View reviewed changes
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@doITmagic doITmagic deleted the copilot/add-community-standards-files-again branch November 23, 2025 09:57
doITmagic pushed a commit that referenced this pull request Mar 7, 2026
fix: address PR #35 review comments
d4a55af 
- Log effective result.Source instead of hardcoded 'file_path' when
  nested_workspace_override is active (comment #1)
- Add TestResolveFilePathNestedWorkspaceOverride to resolver_test.go
  verifying parent root, source, and reduced confidence (comment #2)
- Use TrimRight on entryRoot before appending separator in
  FindParentWorkspace to prevent double separator on root paths
  like '/' or 'C:\' (comment #3)
doITmagic pushed a commit that referenced this pull request Mar 8, 2026
feat(search): add match_reasons annotation (#2 from proposals)
771a034 
- pkg/scoring: DetectMatchReasons() pure function
  - case-insensitive token matching per field (symbol_name/signature/content/docstring)
  - reuses FilterTokens for consistency with rest of scoring package
  - 6 unit tests covering all edge cases

- SmartSearchInput: new include_reasons bool field
- serializeResults/resultToMap: accept query + includeReasons
- match_reasons added to result map only when include_reasons=true
  (zero overhead when not requested)
doITmagic pushed a commit that referenced this pull request Mar 9, 2026
fix: address Copilot PR #40 review comments
52ae5d2 
- Fix nil panic in ContextFromWorkspaceWithStatus when wctx is nil (#7)
- Fix indentation in smart_search_pipeline.go (#1)
- Use loaded idx instead of nil in call_hierarchy.go and find_usages.go (#3, #9)
- Add backward-compat comment on JSON tag mismatch (#6)
- Create fresh IndexStatus when LoadIndexStatus returns nil (#8)
- Populate Elapsed field at completed/failed transitions (#2)
- Throttle progress I/O writes to every 10 files (#4)
- Fix test cleanup for .ragcode dir in TempDir
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

+1 more reviewer

@doITmagic doITmagic doITmagic approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@doITmagic doITmagic

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@doITmagic