Skip to content

[WIP] Add community standards files for Go project#1

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

[WIP] Add community standards files for Go project#1
doITmagic merged 1 commit intomainfrom
copilot/add-community-standards-files

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Nov 23, 2025 •
edited
Loading

Community Standards Files Creation

This PR adds GitHub Community Standards files to improve repository governance and contributor experience.

Plan:

  • Create CODE_OF_CONDUCT.md (Contributor Covenant 2.1)
  • Create CONTRIBUTING.md (Development guide with Go, Docker, Ollama prereqs)
  • Create SECURITY.md (Vulnerability reporting guide)
  • Create .github/ISSUE_TEMPLATE/bug_report.md
  • Create .github/ISSUE_TEMPLATE/feature_request.md
  • Create .github/PULL_REQUEST_TEMPLATE.md

All files will be customized for this Go project that uses Ollama, Qdrant, and Docker.

Original prompt

Create the following Community Standards files for the repository doITmagic/rag-code-mcp to meet GitHub's recommended community standards.

These files should be customized for a Go project that uses Ollama, Qdrant, and Docker.

1. CODE_OF_CONDUCT.md

Create this file in the root directory with the standard Contributor Covenant version 2.1 text.

2. CONTRIBUTING.md

Create this file in the root directory.
Content highlights:

  • Welcome message.
  • Prerequisites: Mention needing Go 1.25+, Docker, and Ollama installed for local development.
  • Development Process:
    1. Fork and clone.
    2. Create a branch.
    3. Make changes.
    4. Run tests: go test ./...
    5. Format code: gofmt -s -w .
    6. Submit PR.
  • Go Standards:
    • Code must be formatted with gofmt.
    • Code must pass go vet.
    • Public functions/types should have comments.
  • Pull Request Process:
    • Describe changes clearly.
    • Update documentation if needed.

3. SECURITY.md

Create this file in the root directory.
Content:

  • Supported Versions: current main branch.
  • Reporting: "Please do not report security vulnerabilities through public GitHub issues." instead "Use the 'Report a vulnerability' button on GitHub or email [maintainer email if known, otherwise generic 'security@example.com' placeholder]." (Use a generic placeholder like maintainers or refer to the GitHub Security tab).

4. .github/ISSUE_TEMPLATE/bug_report.md

Create this file.
Content:

  • YAML header (name: Bug report, about: Create a report to help us improve, labels: bug).
  • Sections:
    • Describe the bug
    • To Reproduce (Steps)
    • Expected behavior
    • Screenshots
    • Environment (Crucial for this project):
      • OS:
      • Go Version:
      • Ollama Version:
      • Qdrant Status (running/stopped):
      • RagCode Version/Commit:
    • Logs

5. .github/ISSUE_TEMPLATE/feature_request.md

Create this file.
Content:

  • YAML header (name: Feature request, about: Suggest an idea, labels: enhancement).
  • Sections:
    • Is your feature request related to a problem?
    • Describe the solution you'd like
    • Describe alternatives you've considered
    • Additional context

6. .github/PULL_REQUEST_TEMPLATE.md

Create this file.
Content:

  • Description (Summary of changes).
  • Type of change (Bug fix, New feature, Breaking change, Documentation update).
  • Checklist:
    • My code follows the style guidelines of this project
    • I have performed a self-review of my own code
    • I have commented my code, particularly in hard-to-understand areas
    • I have made corresponding changes to the documentation
    • I have added tests that prove my fix is effective or that my feature works
    • New and existing unit tests pass locally with my changes

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

Create the following Community Standards files for the repository doITmagic/rag-code-mcp to meet GitHub's recommended community standards.

These files should be customized for a Go project that uses Ollama, Qdrant, and Docker.

1. CODE_OF_CONDUCT.md

Create this file in the root directory with the standard Contributor Covenant version 2.1 text.

2. CONTRIBUTING.md

Create this file in the root directory.
Content highlights:

  • Welcome message.
  • Prerequisites: Mention needing Go 1.25+, Docker, and Ollama installed for local development.
  • Development Process:
    1. Fork and clone.
    2. Create a branch.
    3. Make changes.
    4. Run tests: go test ./...
    5. Format code: gofmt -s -w .
    6. Submit PR.
  • Go Standards:
    • Code must be formatted with gofmt.
    • Code must pass go vet.
    • Public functions/types should have comments.
  • Pull Request Process:
    • Describe changes clearly.
    • Update documentation if needed.

3. SECURITY.md

Create this file in the root directory.
Content:

  • Supported Versions: current main branch.
  • Reporting: "Please do not report security vulnerabilities through public GitHub issues." instead "Use the 'Report a vulnerability' button on GitHub or email [maintainer email if known, otherwise generic 'security@example.com' placeholder]." (Use a generic placeholder like maintainers or refer to the GitHub Security tab).

4. .github/ISSUE_TEMPLATE/bug_report.md

Create this file.
Content:

  • YAML header (name: Bug report, about: Create a report to help us improve, labels: bug).
  • Sections:
    • Describe the bug
    • To Reproduce (Steps)
    • Expected behavior
    • Screenshots
    • Environment (Crucial for this project):
      • OS:
      • Go Version:
      • Ollama Version:
      • Qdrant Status (running/stopped):
      • RagCode Version/Commit:
    • Logs

5. .github/ISSUE_TEMPLATE/feature_request.md

Create this file.
Content:

  • YAML header (name: Feature request, about: Suggest an idea, labels: enhancement).
  • Sections:
    • Is your feature request related to a problem?
    • Describe the solution you'd like
    • Describe alternatives you've considered
    • Additional context

6. .github/PULL_REQUEST_TEMPLATE.md

Create this file.
Content:

  • Description (Summary of changes).
  • Type of change (Bug fix, New feature, Breaking change, Documentation update).
  • Checklist:
    • My code follows the style guidelines of this project
    • I have performed a self-review of my own code
    • I have commented my code, particularly in hard-to-understand areas
    • I have made corresponding changes to the documentation
    • I have added tests that prove my fix is effective or that my feature works
    • New and existing unit tests pass locally with my changes

✨ 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 self-assigned this Nov 23, 2025
@doITmagic doITmagic marked this pull request as ready for review November 23, 2025 09:15
Copilot AI review requested due to automatic review settings November 23, 2025 09:15
Copilot AI reviewed Nov 23, 2025
View reviewed changes
Copy link
Copy Markdown

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 merged commit 15e3d74 into main Nov 23, 2025
2 of 3 checks passed
Copilot AI requested a review from doITmagic November 23, 2025 09:16
@doITmagic doITmagic deleted the copilot/add-community-standards-files 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: path-scoped search + min_score threshold for rag_search
cd66566 
Path-Scoped Search (Proposal #1):
- Results near the agent's file_path get +15% boost (same dir) or +5% (subtree)
- Results from distant subtrees (vendor, inspiration) get -20% penalty
- Pure functions in separate file: scopeDir, pathProximity, applyPathScoping
- 15 unit tests covering all proximity scenarios

Score Threshold (Proposal #7):
- New optional 'min_score' parameter (0.0-1.0) filters low-relevance results
- Auto-threshold: top > 0.70 prunes results below 40% of top score
- Documented in tool description for agent discovery
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
@doITmagic doITmagic mentioned this pull request Mar 18, 2026
Merged
9 tasks
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

@doITmagic doITmagic Awaiting requested review from doITmagic

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