Guidance on getting started with contributing to this project

[C-vam2]

Hi everyone 👋

I’ve been learning Go and would like to start contributing to open-source.

Here’s what I’m currently comfortable with:

• building basic web servers using Gin
• working with MySQL and MongoDB from Go
• basics of concurrency (goroutines, channels, select)

I’d really like to apply these skills to this project, but I’m not sure where to start.

Could you please suggest:
beginner-friendly areas or components in this repository to look at, and any open issues that might be a good first contribution?

Also, if there are any contribution guidelines or setup tips that I should follow, I’d appreciate pointers.

Thanks in advance!

[ismaildasci]

Hey, welcome to open source!

Since you already know how to build web servers with Gin, you are in a good position to contribute. Here are some tips:

Start with CONTRIBUTING.md

The repo has a CONTRIBUTING.md file that explains the basics - read that first. Key points:

• PRs go against master branch
• Keep commits to max 2 (squash if needed)
• Add/update tests for your changes
• New features should be documented in docs/doc.md, not README

Setting up locally

git clone https://github.com/gin-gonic/gin.git
cd gin
make test      # run tests
make fmt       # format code
make vet       # check for suspicious code
make lint      # style checks

The Makefile has all the commands you need. Run make help to see them.

Codebase structure

The main files you should understand:

• gin.go - Engine struct and core server logic
• context.go - the Context object you use in handlers
• routergroup.go - route grouping logic
• binding/ - request binding (JSON, form, etc.)
• render/ - response rendering

Finding issues to work on

Look for issues with help wanted label. There is also #1084 which lists future project goals. You can also:

• Check recent issues/discussions for bugs you can reproduce and fix
• Improve test coverage
• Fix typos or improve documentation in docs/doc.md

With your background

Since you know databases and concurrency, you could look into:

• Issues related to middleware (uses your web server knowledge)
• Performance-related discussions
• Any binding-related issues (since you work with data)

Tips

• Do not start with huge changes, pick something small first
• If you are not sure about an issue, comment and ask before starting
• Make sure tests pass locally before pushing

Good luck!

[MukundaKatta]

Welcome! Skimming the issue tracker, label good first issue is the usual starting point. For Gin specifically, the docs/examples folder and the binding tests are forgiving first PRs. Fork the repo, clone your fork, make test locally to confirm your environment, then pick a small issue and open a PR — the maintainers are responsive.