Scarlett/update contributing

[sattensil]

Important

Updates CONTRIBUTING.md to introduce new contribution paths and improve guidance for contributors.

• New Contribution Paths:
  • Introduces four ways to contribute: picking up existing issues, creating tickets, sharing use cases, and helping on Discord.
• Bug Reports and Feature Requests:
  • Provides detailed instructions for submitting bug reports and feature requests via GitHub issue tracker.
• Community Engagement:
  • Encourages joining Discord for real-time help and contribution discussions.
• Removed Sections:
  • Removes redundant sections on bug reporting and feature requests, consolidating them into new contribution paths.

^{This description was created by for a002241. It will automatically update as commits are pushed.}

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[sattensil]

I have read the CLA Document and I hereby sign the CLA

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to a002241 in 3 minutes and 5 seconds

More details

• Looked at 73 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 6 drafted comments based on config settings.

1. CONTRIBUTING.md:5

• Draft comment:
  Consider minimizing the personal anecdote to maintain a more formal and objective tone. While personal insights can be engaging, a more concise introduction might better serve all contributors.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 80%
  None

2. CONTRIBUTING.md:29

• Draft comment:
  The Discord link is repeated in multiple sections. Consider defining a single reference or variable to ensure consistency and easier maintenance.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 80%
  None

3. CONTRIBUTING.md:17

• Draft comment:
  The guidelines for feature requests and bug reports are clear and helpful. No issues found, but ensure this detailed structure is maintained in future updates.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 80%
  None

4. CONTRIBUTING.md:120

• Draft comment:
  Consider using a lower-level header for 'Questions?' (e.g. '## Questions?') to maintain a consistent document hierarchy, since other sections are not top-level.
• Reason this comment was not posted:
  Confidence changes required: 66% <= threshold 80%
  None

5. CONTRIBUTING.md:5

• Draft comment:
  The first-person anecdote in this section adds a friendly tone, but consider if this personal narrative aligns with your project's overall documentation voice.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 80%
  None

6. CONTRIBUTING.md:37

• Draft comment:
  Multiple H1-level headers (e.g. '# Contributing to Graphiti', '# From Idea to Pull Request', and '# Questions?') may confuse the document structure. Consider using a single H1 for the title and H2 for primary sections for clearer organization.
• Reason this comment was not posted:
  Confidence changes required: 66% <= threshold 80%
  None

Workflow ID: wflow_euSHJjogM6ODOMz1

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.