Add Apitally

[itssimon]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a goreportcard link.

⚠️ Multiple packages are published from the repo, which is why there are no badges for pkg.go.dev / goreportcard in the repo's README, but they are linked below.

• The repo documentation has a coverage service link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link: https://github.com/apitally/apitally-go
• pkg.go.dev:
  • https://pkg.go.dev/github.com/apitally/apitally-go/chi
  • https://pkg.go.dev/github.com/apitally/apitally-go/echo
  • https://pkg.go.dev/github.com/apitally/apitally-go/fiber
  • https://pkg.go.dev/github.com/apitally/apitally-go/gin
• goreportcard.com:
  • https://goreportcard.com/report/github.com/apitally/apitally-go/chi
  • https://goreportcard.com/report/github.com/apitally/apitally-go/echo
  • https://goreportcard.com/report/github.com/apitally/apitally-go/fiber
  • https://goreportcard.com/report/github.com/apitally/apitally-go/gin
• coverage service link: https://codecov.io/gh/apitally/apitally-go

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Updated middleware documentation to include apitally as an available middleware option.

[coderabbitai]

Walkthrough

Added a new entry, "apitally", to the "Actual middlewares" list under Web Frameworks > Middlewares in README.md, including a link and short description.

Changes

Cohort / File(s)	Summary
Documentation list addition README.md	Inserted a new middleware entry ("apitally") with link and description into the "Actual middlewares" list under Web Frameworks > Middlewares.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A nibble of docs, a new friend to tally,
Apitally hops in, light and jolly,
Listed and linked with a cheerful cart,
A tiny change — a big rabbit heart! 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add Apitally' directly and specifically describes the main change: adding Apitally to the list in README.md.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 56e2cfa and 6e789ce.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: quality

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: missing
• goreportcard: missing
• coverage: OK

These checks are a best-effort automation and do not replace human review.