When publishing the project to Github, the Github failure response is swallowed silently

[vittorius]

I tried to publish my “Build my own Claude Code” challenge to GitHub. But, after creating the repo and publishing from a pop-up, nothing appeared in the GitHub repo. I tried that several times (disconnect repo - publish again): all looked like a successful publish but nothing appeared on the target side.

The permissions on the GitHub side were OK; otherwise, the repo wouldn’t show in the drop-down.

Then, I tried to push to the GitHub remote myself and got an error response that I tried to commit a secret, which was true because I played with a test OpenRouter API key of mine for debugging and committed it to the repo. I allowed that key in the GitHub UI and was able to successfully push afterwards.

But that was only a symptom of a problem: it seems that CodeCrafters UI doesn’t show the user that there was a remote problem when publishing the project, along with the error message to resolve the issue.

[whitescreendev]

That’s a good catch. Showing the actual GitHub error would save users a lot of confusion. One other thing worth mentioning is that allowing the push doesn’t make the committed API key safe again. I’d probably rotate that key too, just in case it ends up in the repository history.

[vittorius]

@whitescreendev

I’d probably rotate that key too, just in case it ends up in the repository history.

Yep, GitHub (or GitGuardian?) offers to choose an option “I admit that it’s a valid API key, please whitelist it, I’ll rotate it myself”. Just as I did.