Add blog post: How We Use goose to Maintain goose #6289
Conversation
- Add new blog post about using goose GitHub Action for issue triage - Add Tyler Longwell to authors.yml - Include header image
There was a problem hiding this comment.
Pull request overview
This PR introduces a new blog post documenting how the goose team uses their own AI agent (via a GitHub Action) to automate issue triage and PR creation, along with adding a new author to the team.
Key changes:
- New blog post describing the team's workflow evolution from local goose usage to automated GitHub Action-based issue resolution
- Addition of Tyler Longwell to the authors registry
- Inclusion of header image for the blog post
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
documentation/blog/authors.yml |
Adds Tyler Longwell as a new blog author with proper metadata and social links |
documentation/blog/2025-12-28-goose-maintains-goose/index.md |
New blog post detailing the GitHub Action workflow, recipe phases, and real-world examples of goose maintaining its own repository |
|
|
|
||
| For contributors, responsiveness changes everything. When a user filed [issue #6232](https://github.com/block/goose/issues/6232) about slash commands not handling optional parameters, a maintainer quickly commented `/goose can you fix this`, and within the hour there was a draft PR with the fix and four new tests. Even if the PR is not perfect and needs adjustments, contributors see momentum. | ||
|
|
||
| ## Under the Hood |
There was a problem hiding this comment.
good. recommend reusing this as a Tutorial on the site that walks people through how to set this up on their repo
There was a problem hiding this comment.
brilliant idea. thank you!
|
|
||
| But there's more happening under the hood than a simple prompt like "/goose fix this." | ||
|
|
||
| The workflow uses a [recipe](/docs/guides/recipes) that defines phases to ensure goose actually accomplishes the job and doesn't do more than we ask it to. |
There was a problem hiding this comment.
as a reader, i expected this to link to the actual recipe.
There was a problem hiding this comment.
i agree. fixing this
angiejones
left a comment
angiejones
left a comment
There was a problem hiding this comment.
approved with comments
| @@ -0,0 +1,95 @@ | |||
| --- | |||
| title: How We Use goose to Maintain goose | |||
| description: Learn how an AI agent embedded in GitHub Actions helps maintainers convert issues into PRs. | |||
There was a problem hiding this comment.
The meta description in the frontmatter (line 3) says "convert issues into PRs" while the Open Graph description (line 88) says "triage issues and keep open source moving." These should be consistent for better SEO and social media sharing.
| description: Learn how an AI agent embedded in GitHub Actions helps maintainers convert issues into PRs. | |
| description: Learn how an AI agent embedded in GitHub Actions helps maintainers triage issues and keep open source moving. |
* main: fix: adding more open models (#6300) docs: add goose for vs code extension (#6262) feat(code-mode): use server names for MCP extensions (#6284) docs: agent skills compatibility note (#6299) docs: clarify GOOSE_TERMINAL requires ~/.zshenv for zsh users (#6297) feat: add OpenAI Codex CLI provider (#6263) docs: fix Resources menu (#6292) Remove Advent of AI announcement banner (#6291) Add blog post: How We Use goose to Maintain goose (#6289)
Signed-off-by: James Loope <cronus@stolenshoe.com>
Summary
Adds a new blog post about how the goose team uses goose (via a GitHub Action) to triage issues and maintain the repository.
Changes
documentation/blog/2025-12-28-goose-maintains-goose/index.mdauthors.ymlgoose-maintains-goose.pngBlog Post Structure
Links in the post
Authors: @blackgirlbytes @tlongwell-block