Contribute to gcx

Read AGENTS.md and the authoritative contribution workflow. Use its route and ownership guidance; the contributor does not need to choose a provider, datasource or RFC workflow upfront.

1. Establish the current step

Identify the requested outcome and the existing issue, accepted decisions, RFC or implementation branch. Inspect those records and relevant code before asking questions. State the applicable route, current step and missing maintainer decision. Reuse settled scope and design at each handoff.

Work within the request and existing authorization. A draft-only or review-only request ends with that artifact. An implementation request continues through authorized work once applicable maintainer decisions are settled. Prepare the concrete result before requesting publication permission; reuse authorization already given for the same destination and scope.

2. Prepare the issue when the route needs one

Documentation changes and bug fixes can go directly to a PR. Other code contributions need an accepted issue; comment on it to coordinate the work. Follow the product-team exception for changes within an existing owned area.

Search the repository’s open and closed issues for existing reports and proposals before creating an issue or starting implementation. Reuse a relevant issue; check its outcome and maintainer decisions before proceeding. When its maintainer decision is settled, continue to the needed planning or implementation rather than drafting another proposal.

• Bugfixes: can go directly to a PR without a separate issue or prior maintainer acknowledgement. When reporting a bug, search for an existing report first and add relevant evidence there. If no report matches, use the Bug report form. Establish actual and expected behavior, reproduction or evidence, and relevant version/environment. Link the existing report from the fix PR when available. Record verified findings separately from assumptions.
• Feature: use propose-feature to research and draft the common proposal. Show a concrete problem, proposed UX and checkable acceptance criteria; scale examples to the work and identify unresolved facts.