storeapi: fix typo
Metadata
Current evaluation
Merged PR #3667 via commit 911bf4698 (merge 0224b48ea), correcting a typo in the storeapi module.
Resolution: closed resolved
Reason: PR #3667 corrected the one-line storeapi typo and was merged into main as commit 911bf4698.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? -> No, but I am an employee of Canonical.
- [ ] Have you successfully run `./runtests.sh static`?
- [ ] Have you successfully run `./runtests.sh tests/unit`?
No and no - I assume CI will do this for me :-)
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #3667 via commit 911bf4698 (merge 0224b48ea), correcting a typo in the storeapi module. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #3667 via commit 911bf4698, correcting a single typo in the storeapi module. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a single-line typo correction in the storeapi module. Approved by a reviewer, passed CI, and increased test coverage by 0.07%. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a typo fix in the storeapi module. The contributor skipped local tests, relying on CI. A maintainer confirmed unrelated CI errors were non-blocking. The merge increased overall code coverage by 0.07%. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2116 storeapi: handle 5xx error codes for all store endpoints | snapcraft | merged | Merged PR #2116 as commit c6500ca0e, generalizing Store API 5xx handling across all endpoints and fixing LP #1768370. | |
| #3442 storeapi: reduce the amount of constants and their meaning | snapcraft | merged | Merged PR #3442 in commit cee67ae16, reducing storeapi URL constants to root URLs, using full endpoint paths where needed, and renaming constants for backend clarity. |