Fix Security section alphabetical order - #6591
Conversation
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR |
Automated Quality ChecksRequired checks❌ Repo link: missing from PR body
Forge link: https://github.com/your-org/your-project ❌ Go Report Card: missing from PR body
goreportcard.com: https://goreportcard.com/report/github.com/your-org/your-project Popular options: Codecov, Coveralls. Integrate one with your CI to track coverage automatically.
These checks are automated and do not replace maintainer review. See CONTRIBUTING.md for full guidelines. PR Diff ValidationContent checks✅ Files changed: only README.md Warnings
Automated diff validation — does not replace maintainer review. |
PR Summary by QodoRestore alphabetical order in README Security tools list
AI Description
High-Level Assessment
Files changed (1)
|
Qodo FixerNo findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR. |
|
CI note: |
Fix the pre-existing
TestAlphafailure onmainby restoring alphabetical order in the Security section:acme-proxymust precedeacmetool.This maintenance fix is intentionally separate from #6590 so that the package submission continues to change exactly one item.
Validation:
go test main_test.go main.go