Release 0.0.3

[waynehamadi]

Background

Changes

PR Quality Checklist

• I have run the following commands against my code to ensure it passes our linters:

  black . --exclude test.py
  isort .
  mypy .
  autoflake --remove-all-unused-imports --recursive --ignore-init-module-imports --ignore-pass-after-docstring --in-place agbenchmark

[github-actions]

PR Analysis

• 🎯 Main theme: Version update
• 📌 Type of PR: Enhancement
• 🧪 Relevant tests added: No
• ✨ Focused PR: Yes, because the PR has a clear title and description, and the changes in the code are directly related to the title and description, which is updating the version of the project.
• 🔒 Security concerns: No, because the changes made in this PR are related to the version update in the project configuration file and do not involve any code that could potentially introduce security issues.

PR Feedback

• 💡 General PR suggestions: The PR is well-structured and follows good practices. However, it would be beneficial to include a brief summary of the changes or improvements that led to the version update in the description. This would provide more context to the version update and make it easier for others to understand the changes.

How to use

To invoke the PR-Agent, add a comment using one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve: Suggest improvements to the code in the PR.
/ask <QUESTION>: Pose a question about the PR.

To edit any configuration parameter from 'configuration.toml', add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."