feat(platform): Add Get Linear Issues Block

[Swiftyos]

Added the ability to get all issues for a given project.

Changes 🏗️

• added api query
• added new models
• added new block that gets all issues for a given project

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • I have ensured the new block works in dev
  • I have ensured the other linear blocks still work

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	07697f6
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/6920c322fe0454000831fe83

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch swiftyos/get-linear-issues

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	07697f6
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/6920c322c4719b00084aa3fa

[deepsource-io]

Here's the code health analysis summary for commits 0edc669..07697f6. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Issue The GraphQL filter for assignee uses assignee: { null: $isAssigned } but the variable is passed as not is_assigned. This inversion is non-obvious and likely incorrect or at least confusing; if is_assigned=True, the filter becomes null: False (assigned), which is easy to misinterpret and could drift with future changes. Consider renaming the input or removing the inversion to align semantics clearly. variables: dict[str, Any] = { "projectName": project, "statusName": status, "isAssigned": not is_assigned, "includeComments": include_comments, Output Contract The block yields both an issues list and individual issue items, but Output schema defines a single issue: Issue (not a stream/array). Emitting multiple issue outputs may violate the expected schema/consumer assumptions. Confirm that downstream supports multiple emissions for the same key or adjust the output schema to a list-only or singular mode. yield "issues", issues for i in issues: yield "issue", i Backward Compatibility The Project model fields changed from required types to optional (e.g., description, priority, progress). This can affect code relying on non-null values. Validate all usages for None handling to avoid runtime errors. id: str name: str description: str | None = None priority: int | None = None progress: float | None = None content: str | None = None

[AutoGPT-Agent]

Thank you for your contribution! I noticed some issues that need to be addressed before this PR can be merged:

1. Title/Content Mismatch: Your PR title is about removing un-runnable agents from a schedule, but the code changes are actually adding Linear API functionality to get project issues. Please update your PR title to accurately reflect the changes, following the conventional commit format (e.g., feat(platform/blocks): Add Linear project issues query functionality).

2. Changes Description: While your description mentions adding an API query, new models, and a new block (which matches the code), it should be more specific about what this functionality does. Consider mentioning that you're adding a new Linear integration feature to get project issues filtered by status and assignee.

3. Test Coverage: Your test plan only mentions verifying that the new block works in dev and that other Linear blocks still work. Consider adding more specific test scenarios for this feature, such as:

   • Testing with different project names
   • Testing with various status filters
   • Testing with both assigned and unassigned issues
   • Testing with and without comments

Once you align the PR title with the actual changes and enhance the description and test plan, this should be ready for another review.

[AutoGPT-Agent]

Thank you for your PR adding the Linear Issues Block functionality! The implementation looks good and your changes are focused on the specific feature.

Just one small note: The PR title should use "feat" instead of "feature" to conform to the conventional commit format. Consider updating it to: "feat(platform): Add Get Linear Issues Block"

Otherwise, your PR is well-documented with a clear description and completed checklist. The test plan is appropriate for the changes made. The implementation adds the necessary API query, models, and block functionality in a clean and organized way.