Skip to content

Moving to issues as the new PRs - #10818

Merged
DOsinga merged 5 commits into
mainfrom
codex/blog-issues-are-the-new-prs
Jul 30, 2026
Merged

DOsinga merged 5 commits into
mainfrom
codex/blog-issues-are-the-new-prs

Conversation

@DOsinga

@DOsinga DOsinga commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add a blog post explaining goose’s move toward issue-led contributions
  • feature the post on the blog landing page
  • add a hero image showing the current pull request volume

Verification

  • previewed locally with Docusaurus
  • confirmed the post and hero image return HTTP 200

@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview deployed: https://pr-10818.goose-pr-previews-poc.pages.dev

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a8db5932d8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".


We’re moving goose to this model with a public [Goose Issues board](https://github.com/orgs/aaif-goose/projects/1). As before, if you find a bug or want a new feature, you [file a GitHub issue](https://github.com/aaif-goose/goose/issues/new/choose). New issues enter the Inbox. During triage we may ask for more information or close the issue with an explanation. Problems we want to solve move to Accepted / design, where contributors and the core team work out the intended design, architectural constraints and how the result will be verified.

When that discussion has settled, the issue moves to Ready. At that point an agent can write the code. The issue moves to In progress while implementation is underway and Verification when the result is ready for a human to confirm that it works. Only then is it Done. PRs that do not implement a ready issue will be closed, as will PRs where [feedback is left unaddressed](https://github.com/aaif-goose/goose/blob/main/CONTRIBUTING.md#ai-code-reviews).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Synchronize the contribution guide with the ready-issue policy

When contributors rely on the repository's canonical instructions, they are still told that general pull requests are welcome, that linking an issue is merely beneficial, and to open a PR once a concrete change is ready (CONTRIBUTING.md:5-7, CONTRIBUTING.md:22-23, and CONTRIBUTING.md:47-54). This directly conflicts with the newly announced rule that every PR without a Ready issue will be closed, so contributors can follow the documented process and waste implementation effort; update the contribution guide as part of this policy rollout.

Useful? React with 👍 / 👎.


To preserve that value, we have to let go of the PR as the main contribution mechanism and move outside contribution upstream. The valuable place to contribute is no longer primarily in writing the code, but in filing good issues and, more importantly, taking part in the discussion that turns those issues into well-considered solutions.

We’re moving goose to this model with a public [Goose Issues board](https://github.com/orgs/aaif-goose/projects/1). As before, if you find a bug or want a new feature, you [file a GitHub issue](https://github.com/aaif-goose/goose/issues/new/choose). New issues enter the Inbox. During triage we may ask for more information or close the issue with an explanation. Problems we want to solve move to Accepted / design, where contributors and the core team work out the intended design, architectural constraints and how the result will be verified.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Lowercase the product name in the board label

Change Goose Issues board to goose Issues board (or rephrase the label), because the documentation-specific brand rule requires the product name to always use a lowercase g, including in blog posts and all other documentation content.

AGENTS.md reference: documentation/AGENTS.md:L3-L10

Useful? React with 👍 / 👎.

@alexhancock alexhancock self-assigned this Jul 30, 2026
@DOsinga
DOsinga added this pull request to the merge queue Jul 30, 2026
Merged via the queue into main with commit 2859dc8 Jul 30, 2026
24 checks passed
@DOsinga
DOsinga deleted the codex/blog-issues-are-the-new-prs branch July 30, 2026 18:58
lifeizhou-ap added a commit that referenced this pull request Jul 31, 2026
* main:
  fix(desktop): allow removing images when editing user messages (#9979)
  Fetch cursor-agent models from CLI (#10367)
  fix(cerebras): preserve thinking inline for models that reject reasoning_content (#10774)
  perf: make CLI streaming render incremental instead of O(n^2) (#10487)
  Moving to issues as the new PRs (#10818)
  ci: defer privileged recipe scans for forks (#10825)
  docs: adopt issue-first contribution workflow (#10819)
  Add Azure AI Foundry multi-LLM provider (#10622)
  fix(together): parse model list response (#10576)
  docs: remove retired site resources (#10817)
  feat: streaming shell output while commands run (#10808)
lifeizhou-ap added a commit to vincenzopalazzo/edvige that referenced this pull request Jul 31, 2026
* main: (224 commits)
  fix(desktop): allow removing images when editing user messages (aaif-goose#9979)
  Fetch cursor-agent models from CLI (aaif-goose#10367)
  fix(cerebras): preserve thinking inline for models that reject reasoning_content (aaif-goose#10774)
  perf: make CLI streaming render incremental instead of O(n^2) (aaif-goose#10487)
  Moving to issues as the new PRs (aaif-goose#10818)
  ci: defer privileged recipe scans for forks (aaif-goose#10825)
  docs: adopt issue-first contribution workflow (aaif-goose#10819)
  Add Azure AI Foundry multi-LLM provider (aaif-goose#10622)
  fix(together): parse model list response (aaif-goose#10576)
  docs: remove retired site resources (aaif-goose#10817)
  feat: streaming shell output while commands run (aaif-goose#10808)
  feat(acp): allow session/new to request a Hidden session via _meta.hidden (aaif-goose#10811)
  chore: removed stale text pnpm workspace (aaif-goose#10809)
  feat(otel): emit GenAI semantic convention attributes (aaif-goose#10700)
  fix: avoid double loading full conversation on session open (aaif-goose#10794)
  feat(providers): forward images and MCP embedded-resource blobs in Anthropic and Google formats (aaif-goose#10340)
  Deprecate and remove ui/text TUI (aaif-goose#10799)
  Upgrade to rmcp 3.0 (aaif-goose#10789)
  fix(release): signing environment (aaif-goose#10797)
  feat(tools): collapse const-union enums in tool schemas (aaif-goose#10577)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants