Contributing

Go-Spring is an open-source community-driven project. Code, documentation, examples, issues, feature requests, and usage feedback are all welcome.

Contributors

Go-Spring grows with every participant. This section records the project author, maintainers, and important contributors.

Author

Liang Huan

Author and primary maintainer of Go-Spring.

• GitHub: lianghuan
• Focus areas: Go engineering, microservice infrastructure, framework design

More contributors

Meaningful PRs, issues, documentation improvements, and usage feedback are welcome. More contributor profiles will be added here over time.

How to participate

• Open issues to report problems or propose requirements
• Improve documentation, examples, or tutorials
• Fix bugs or add tests
• Contribute new features or infrastructure integrations

Before submitting

Before contributing code, read the repository root CODING_STYLE.md to understand the project coding conventions.

Before submitting a PR, please run the necessary tests and keep the change simple, clear, and direct.

Recording gotchas

Gotchas hit while working with AI, or during everyday development, that are worth helping others avoid should be recorded as GitHub issues — one issue per gotcha, each with its own timeline, discussion, and resolution, naturally searchable and linkable.

• How to record: open an issue, add the gotcha label, put the symptom in the title, and describe the trigger scenario, cause, and workaround in the body.
• How to find: check the label filter page, which always holds the latest complete list — all issues labeled gotcha.
• When to promote: if the workaround for a gotcha becomes "no judgment needed, just do it", distill it into the repository root CLAUDE.md and close the issue.