Skip to content

Conversation

@corbob
Copy link
Member

@corbob corbob commented Oct 31, 2025

Description Of Changes

This adds a Common Errors page for CCR documentation.

Motivation and Context

Document the known HTTP error responses from CCR to help users identify reasons for push failures.

Testing

  • I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

  • Minor documentation fix (typos etc.).
  • Major documentation change (refactoring, reformatting or adding documentation to existing page).
  • New documentation page added.
  • The change I have made should have a video added, and I have raised an issue for this.
    • Issue #

Change Checklist

  • Requires a change to menu structure (top or left-hand side)/
  • Menu structure has been updated
  • Images added to the img repository?
    • PR -

Related Issue

Fixes #426

@corbob corbob requested a review from gep13 October 31, 2025 14:02
order: 50
xref: ccr-common-errors
title: Common Errors Encountered
description: descriptiono
Copy link
Member

Choose a reason for hiding this comment

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

This doesn't feel like it was completed.

Copy link
Member Author

Choose a reason for hiding this comment

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

That would be accurate. I was trying to get a preview up and it didn't like that I left the description blank 😂 I'll get this fixed up.

import Iframe from '@choco-astro/components/Iframe.astro';
import Xref from '@components/Xref.astro';

## You've pushed a package, but got an error?
Copy link
Member

Choose a reason for hiding this comment

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

This doesn't feel like a question. Perhaps

Suggested change
## You've pushed a package, but got an error?
## Have you pushed a package and got an error?


## Error 400 Bad Request

Can occur if the API Key is not a validly formatted GUID, or the package you've attempted to push contains a non-normalized version number.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Can occur if the API Key is not a validly formatted GUID, or the package you've attempted to push contains a non-normalized version number.
Can occur if the API Key is not a correctly formatted GUID, or the package you've attempted to push contains a non-normalized version number.

## Error 500 Internal Server Error

If you receive a `500 Internal Server Error` when pushing a package, you may have a malformed package that the server was unable to process.
One such case is documented in a [GitHub issue](https://github.com/chocolatey/home/issues/303).
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
One such case is documented in a [GitHub issue](https://github.com/chocolatey/home/issues/303).
One such case is documented in this [GitHub issue](https://github.com/chocolatey/home/issues/303).

@gep13 gep13 requested a review from st3phhays November 3, 2025 10:51
@gep13
Copy link
Member

gep13 commented Nov 3, 2025

@st3phhays since there is a new page getting added here, can I get you to have a look over this PR as well, just to make sure that nothing jumps out at you. Thanks!

---
order: 50
xref: ccr-common-errors
title: Common Errors Encountered
Copy link
Member

Choose a reason for hiding this comment

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

I noticed in other parts of our docs, we say "Common Errors and Resolutions". Would this be a better name for this page?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure we provide many resolutions here, but more than happy to use it for consistency, and we can always add more resolutions in the future.

@corbob corbob requested review from gep13 and st3phhays November 3, 2025 19:37
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.

Add documentation around common causes for some of the HTTP failure status codes from Community Repository

3 participants