mirror of https://github.com/Significant-Gravitas/AutoGPT.git synced 2026-01-29 00:48:01 -05:00

Files

Nicholas Tindle 90466908a8 refactor(docs): restructure platform docs for GitBook and remove MkDo… (#11825 )

<!-- Clearly explain the need for these changes: -->
we met some reality when merging into the docs site but this fixes it
### Changes 🏗️
updates paths, adds some guides
<!-- Concisely describe all of the changes made in this pull request:
-->
update to match reality
### Checklist 📋

#### For code changes:
- [x] I have clearly listed my changes in the PR description
- [x] I have made a test plan
- [x] I have tested my changes according to the test plan:
  <!-- Put your test plan here: -->
  - [x] deploy it and validate

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Aligns block integrations documentation with GitBook.
> 
> - Changes generator default output to
`docs/integrations/block-integrations` and writes overview `README.md`
and `SUMMARY.md` at `docs/integrations/`
> - Adds GitBook frontmatter and hint syntax to overview; prefixes block
links with `block-integrations/`
> - Introduces `generate_summary_md` to build GitBook navigation
(including optional `guides/`)
> - Preserves per-block manual sections and adds optional `extras` +
file-level `additional_content`
> - Updates sync checker to validate parent `README.md` and `SUMMARY.md`
> - Rewrites `docs/integrations/README.md` with GitBook frontmatter and
updated links; adds `docs/integrations/SUMMARY.md`
> - Adds new guides: `guides/llm-providers.md`,
`guides/voice-providers.md`
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
fdb7ff8111. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>
Co-authored-by: bobby.gaffin <bobby.gaffin@agpt.co>

2026-01-23 06:18:16 +00:00

1.3 KiB

Raw Blame History

Linear Comment

Blocks for creating and managing comments on Linear issues.

Linear Create Comment

What it is

Creates a new comment on a Linear issue

How it works

This block creates a new comment on a Linear issue using the Linear GraphQL API. Provide the issue ID and comment text, and the block posts the comment and returns its ID.

Comments appear in the issue's activity timeline and notify relevant team members.

Inputs

Input	Description	Type	Required
issue_id	ID of the issue to comment on	str	Yes
comment	Comment text to add to the issue	str	Yes

Outputs

Output	Description	Type
error	Error message if the operation failed	str
comment_id	ID of the created comment	str
comment_body	Text content of the created comment	str

Possible use case

Automated Updates: Post status updates or progress reports to issues automatically.

Integration Comments: Add comments when external systems (CI/CD, monitoring) detect relevant changes.

Cross-Tool Communication: Post comments from chatbots or customer support integrations.

1.3 KiB Raw Blame History