Skip to content

Conversation

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jul 28, 2025

- What I did

Removed the error return from the ParseRepositoryInfo function. There are no validation steps inside ParseRepositoryInfo which could cause an error, so we always returned a nil error.

- How I did it

- How to verify it

- Human readable description for the release notes

- A picture of a cute animal (not mandatory but encouraged)

@thaJeztah thaJeztah added this to the 29.0.0 milestone Jul 28, 2025
@thaJeztah thaJeztah added status/2-code-review kind/refactor PR's that refactor, or clean-up code labels Jul 28, 2025
@codecov-commenter
Copy link

Codecov Report

❌ Patch coverage is 45.45455% with 6 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
cli/registry/client/fetcher.go 0.00% 2 Missing ⚠️
cli/command/plugin/push.go 0.00% 1 Missing ⚠️
cli/command/service/trust.go 0.00% 1 Missing ⚠️
cli/registry/client/endpoint.go 0.00% 1 Missing ⚠️
cli/trust/trust.go 0.00% 1 Missing ⚠️

📢 Thoughts on this report? Let us know!

@thaJeztah
Copy link
Member Author

I think I had a bunch of follow-up changes stashed locally, but I didn't finish pushing those as a PR yet in the weekend; let's get this one in first.

/cc @Benehiko

@thaJeztah thaJeztah requested a review from Benehiko July 28, 2025 06:53
Copy link
Member

@Benehiko Benehiko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We just need a description I think on the PR body

@thaJeztah
Copy link
Member Author

We just need a description I think on the PR body

Heh; not sure what to put in the body that's not already described in the first line. Something you had in mind?

@Benehiko
Copy link
Member

We just need a description I think on the PR body

Heh; not sure what to put in the body that's not already described in the first line. Something you had in mind?

I updated the PR body, we can merge if you're happy with the description.

Removed the error return from the `ParseRepositoryInfo` function.
There are no validation steps inside `ParseRepositoryInfo` which
could cause an error, so we always returned a nil error.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah force-pushed the ParseRepositoryInfo_no_err branch from 2ff70a5 to 86b5b52 Compare July 29, 2025 16:32
@thaJeztah thaJeztah changed the title internal/registry: ParseRepositoryInfo: remove error return internal/registry: ParseRepositoryInfo: remove unused error return Jul 29, 2025
@thaJeztah thaJeztah merged commit a0ae6e6 into docker:master Jul 29, 2025
90 checks passed
@thaJeztah thaJeztah deleted the ParseRepositoryInfo_no_err branch July 29, 2025 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/refactor PR's that refactor, or clean-up code status/2-code-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants