Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: added basic comparison docs page #220

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

ErikBjare
Copy link
Owner

@ErikBjare ErikBjare commented Oct 23, 2024

Fixes #112


Important

Adds comparison.rst to document gptme features and compare it with other AI-assisted development tools.

  • Documentation:
    • Adds comparison.rst to provide an overview of gptme and similar AI-assisted development tools.
    • Highlights key features of gptme, such as terminal operation, shell command execution, and extensibility.
    • Compares gptme with alternatives like Open Interpreter, Aider, Moatless Tools, GPT Engineer App, and Cursor.
    • Discusses differences in focus, environment, and capabilities between gptme and other tools.
    • Provides guidance on choosing the right tool based on user needs and preferences.

This description was created by Ellipsis for a6f91bd. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

👍 Looks good to me! Reviewed everything up to a6f91bd in 13 seconds

More details
  • Looked at 152 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 3 drafted comments based on config settings.
1. docs/comparison.rst:28
  • Draft comment:
    Typo: Change 'which be more what you are looking for' to 'which may be more what you are looking for.'
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The phrase 'which be more what you are looking for' is grammatically incorrect. It should be 'which may be more what you are looking for.'
2. docs/comparison.rst:84
  • Draft comment:
    Avoid using question marks in statements. Consider rephrasing to provide clear differences without uncertainty.
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The question marks in the differences section suggest uncertainty. It's better to provide clear and confident statements.
3. docs/comparison.rst:124
  • Draft comment:
    Clarify 'this seems to be it.' Consider rephrasing to specify what 'it' refers to, such as 'Cursor might be the right choice for you.'
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The phrase 'If you are a VSCode user who doesn't mind using a fork, this seems to be it.' is informal and unclear. It should be more precise about what 'it' refers to.

Workflow ID: wflow_hvFF3E6O8HgUMi6L


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

@codecov-commenter
Copy link

codecov-commenter commented Oct 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.38%. Comparing base (d7cebba) to head (a6f91bd).
Report is 3 commits behind head on master.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #220      +/-   ##
==========================================
+ Coverage   75.11%   75.38%   +0.27%     
==========================================
  Files          57       57              
  Lines        3580     3591      +11     
==========================================
+ Hits         2689     2707      +18     
+ Misses        891      884       -7     
Flag Coverage Δ
anthropic/claude-3-haiku-20240307 74.40% <ø> (+0.27%) ⬆️
openai/gpt-4o-mini 73.87% <ø> (-0.06%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

Make a feature comparison table with alternatives
2 participants