Required Contribution Setup
All valid contributions to the FastGPT open source repository must originate from a forked copy of the official FastGPT repository. The official, canonical source code is hosted at https://github.com/labring/FastGPT. You must create your forked repository from this exact location to ensure your changes align with the project’s core codebase and meet contribution eligibility requirements.
Step-by-Step Contribution Workflow
Follow this structured, official process to submit eligible contributions:
- Fork the official FastGPT repository to your personal GitHub account.
- Develop code changes or fixes that target a single, specific issue to avoid scope creep.
- Commit your changes using small, focused commits: each commit should resolve only one distinct issue, to simplify review and cross-team tracking of changes.
- Push your committed changes to your forked GitHub repository.
- Open a pull request (PR) against the main branch of the official FastGPT repository. The FastGPT team and community will collaborate directly with you to review your submission and address any feedback.
If you encounter merge conflicts during the PR review process, refer to GitHub’s official pull request tutorial at https://docs.github.com/en/pull-requests/collaborating-with-pull-requests for step-by-step guidance on resolving conflicts and updating your PR.
Post-Merge Contributor Recognition
Once your pull request is successfully merged into the official FastGPT main branch, your GitHub account will be added to the official FastGPT contributors table. This table is publicly accessible at https://github.com/labring/FastGPT/graphs/contributors, and serves as a permanent public record of all community contributions to the project.
Source: FastGPT official source
Applicability and version scope
Use this page for the documented Deployment and upgrades scenario. Confirm the FastGPT, dependency, API, and deployment versions in the official source before applying a change.
Safety guardrails
Use [REDACTED_CREDENTIAL] for credentials and private data. Confirm the documented environment and version before review.
Rollback guidance
Restore the prior technical-content authority snapshot. Restore saved configuration and data snapshots, then repeat the smallest verification scenario.