Contribute to Gonex
Set up the Gonex framework repository, understand its internals and contribute tested changes to the framework itself.
This section is for developing Gonex itself: its application lifecycle, typed transports, generators, integrations and release tooling.
If you want to build your own API application, start with Build with Gonex. Installing the package in an application does not require a fork of the framework.
Contributor path
- Set up the framework repository.
- Read Framework internals before choosing where a change belongs.
- Run the relevant tests and checks.
- Prepare a focused pull request with a clear problem and actual verification results.
- Maintainers use Maintaining releases for release gates and compatibility policy.
Useful contributions
Bug fixes with reproductions, clearer consumer examples, better error messages, stronger typed-contract validation and focused tests can all be useful. For a larger public API or architectural change, open an issue to discuss the behavior and compatibility implications before committing to an implementation.
The upstream source repository is amkargar/gonex. This documentation website lives separately in amkargar/GoNex-website. Submit framework changes to the former and website/docs presentation changes to the latter.