Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve "not found" error messages #2112

Merged
merged 2 commits into from
Aug 1, 2024

Conversation

szokeasaurusrex
Copy link
Member

Fixes #2111

szokeasaurusrex added a commit that referenced this pull request Aug 1, 2024
Clarify that users need to check the release, project, and organization when encountering a "release not found" error, since any of these being wrong can cause a "release not found" error.

Fixes #2111
szokeasaurusrex added a commit that referenced this pull request Aug 1, 2024
Update "project not found" message to avoid mentioning "IDs" and "slugs," which might confuse some users. Instead, make this error message follow the same format as the "release not found" message.
@szokeasaurusrex szokeasaurusrex force-pushed the szokeasaurusrex/release-not-found branch from c72fbc7 to 2fd6f2f Compare August 1, 2024 09:03
src/api/errors/api_error.rs Outdated Show resolved Hide resolved
Clarify that users need to check the release, project, and organization when encountering a "release not found" error, since any of these being wrong can cause a "release not found" error.

Fixes #2111
Update "project not found" message to avoid mentioning "IDs" and "slugs," which might confuse some users. Instead, make this error message follow the same format as the "release not found" message.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve "release not found" error message
2 participants