Merge branch 'memory-v2-dict-fix-ag-3058' of https://github.com/agno-agi/agno into memory-v2-dict-fix-ag-3058

Author: dirkbrnd

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,98 @@
+name: Bug Report
+description: Report an issue to help us fix bugs and improve your experience.
+title: "[Bug] "
+labels: ["bug"]
+assignees:
+  - ""
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! Please provide as much detail as possible.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Briefly describe the issue you’re experiencing or the bug you’ve found.
+      placeholder: A clear and concise description of what the bug is.
+    validations:
+      required: true
+  - type: textarea
+    id: steps-to-reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: List the exact steps needed to encounter this bug or issue.
+      placeholder: |
+        1. Go to '...'
+        2. Click on '....'
+        3. Scroll down to '....'
+        4. See error
+    validations:
+      required: true
+  - type: textarea
+    id: agent-config
+    attributes:
+      label: Agent Configuration (if applicable)
+      description: If the bug relates to a specific agent setup, provide relevant configuration details.
+      placeholder: |
+        ```python
+        # Your agent configuration code here
+        ```
+    validations:
+      required: false
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+      placeholder: A clear description of what you expected.
+    validations:
+      required: true
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: Actual Behavior
+      description: What actually happened instead?
+      placeholder: A clear description of what happened.
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Screenshots or Logs (if applicable)
+      description: Include any relevant screenshots or error logs that demonstrate the issue. Use code blocks for logs.
+      placeholder: |
+        ```log
+        Paste your logs here
+        ```
+        (You can also drag and drop images)
+    validations:
+      required: false
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Please provide details about the environment where you encountered the bug.
+      placeholder: |
+        - OS: [e.g. macOS Sonoma, Windows 11]
+        - Browser (if relevant): [e.g. Chrome 120, Firefox 119]
+        - Agno Version: [e.g. v0.5.1]
+        - External Dependency Versions: [e.g., openai 1.3.5, langchain 0.0.350]
+        - Additional Environment Details: [e.g., Python 3.11.5]
+      render: markdown
+    validations:
+      required: true
+  - type: textarea
+    id: possible-solutions
+    attributes:
+      label: Possible Solutions (optional)
+      description: Suggest any ideas you might have to fix or address the issue.
+    validations:
+      required: false
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Add any other context or details about the problem here.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Ask a question or discuss
+    url: https://community.agno.com/ 
+    about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,52 @@
+name: Feature Request
+description: Suggest a feature or enhancement to make Agno even better.
+title: "[Feature Request] "
+labels: ["enhancement"]
+assignees:
+  - ""
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting an idea! Please describe your feature request in detail.
+  - type: textarea
+    id: problem-description
+    attributes:
+      label: Problem Description
+      description: Provide a clear and concise explanation of the problem or limitation you're facing. Why is this feature needed?
+      placeholder: "Example: I often find it frustrating when [...] because [...]"
+    validations:
+      required: true
+  - type: textarea
+    id: proposed-solution
+    attributes:
+      label: Proposed Solution
+      description: Explain your ideal solution. How should this feature work? Be as detailed as possible.
+      placeholder: Describe how the feature should function, potential UI changes, API design, etc.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives-considered
+    attributes:
+      label: Alternatives Considered
+      description: Have you found any workarounds or alternative solutions? Share other approaches you've tried or thought about.
+    validations:
+      required: false
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Include any extra information that might be helpful (screenshots, examples of similar features elsewhere, relevant links).
+    validations:
+      required: false
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Would you like to work on this?
+      description: We welcome contributions! Let us know if you’d like to help implement this feature.
+      options:
+        - label: Yes, I’d love to work on it!
+        - label: I’m open to collaborating but need guidance.
+        - label: No, I’m just sharing the idea.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,22 @@
+name: PR Lint
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize]
+
+jobs:
+  lint-pr:
+    name: Lint PR Title and Body
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check PR Title Format
+        run: |
+          TITLE="${{ github.event.pull_request.title }}"
+          REGEX="^(\[(feat|fix|docs|test|refactor|build|ci|chore|perf|style|revert)\]\\s*.+|(feat|fix|docs|test|refactor|build|ci|chore|perf|style|revert):\\s*.+)"
+          if [[ ! "$TITLE" =~ $REGEX ]]; then
+            echo "❌ PR Title '$TITLE' does not match the required format '[type] subject' or 'type: subject'."
+            echo "   Please start your PR title with a valid type like [feat], [fix], feat:, fix:, etc., followed by a space and the subject."
+            exit 1
+          else
+            echo "✅ PR Title format is valid."
+          fi

.github/ISSUE_TEMPLATE/feature_request.md

@@ -8,10 +8,22 @@ Please follow the [fork and pull request](https://docs.github.com/en/get-started
 
 - Fork the repository.
 - Create a new branch for your feature.
-- Add your feature or improvement.
-- Send a pull request.
-- We appreciate your support & input!
+  - Add your feature or improvement.
+  - **Ensure your Pull Request follows our guidelines (see below).**
+  - Send a pull request.
+  - We appreciate your support & input!
 
+## Pull Request Guidelines
+
+To maintain a clear and organized project history, please adhere to the following guidelines when submitting Pull Requests:
+
+1.  **Title Format:** Your PR title must start with a type tag enclosed in square brackets, followed by a space and a concise subject.
+    - Example: `[feat] Add user authentication`
+    - Valid types: `[feat]`, `[fix]`, `[docs]`, `[test]`, `[refactor]`, `[build]`, `[ci]`, `[chore]`, `[perf]`, `[style]`, `[revert]`.
+2.  **Link to Issue:** The PR description should ideally reference the issue it addresses using keywords like `fixes #<issue_number>`, `closes #<issue_number>`, or `resolves #<issue_number>`.
+    - Example: `This PR fixes #42 by implementing the new login flow.`
+
+_These guidelines are enforced automatically by our [PR Lint workflow](.github/workflows/pr-lint.yml)._
 
 ## Development setup
 

.github/workflows/pr-lint.yml

@@ -12,6 +12,7 @@ def get_upcoming_spacex_launches(num_launches: int = 5) -> str:
     launches = sorted(launches, key=lambda x: x["date_unix"])[:num_launches]
     return json.dumps(launches, indent=4)
 
+
 # Create an Agent that has access to real-time SpaceX data
 agent = Agent(
     model=OpenAIChat(id="gpt-4.1"),