How to Commit Changes Using CMD Without Pushing in Your GitHub Project

Select Language:

If you’re having trouble with GitHub rejecting your code due to a “Repository is Read-Only” error, don’t worry. This issue often happens when your permissions are limited or when access rights change. Here’s how you can resolve it and regain the ability to push updates:

First, make sure you’re logged into the correct GitHub account that has write access to the repository. Sometimes, being logged into a different account can cause this problem.

Next, check your permissions for the repository. If you’re not the owner, you may need to request write access from the repository administrator.

If you do have proper permissions, verify your remote URL. Use the command git remote -v in your terminal to see the current repository URL. If it’s set to a read-only URL (like HTTPS with a read-only token or SSH with limited rights), update it to a writable URL.

To change the remote URL, run:
bash
git remote set-url origin

Replace <your-writable-repo-url> with the HTTPS or SSH URL that grants write access.

Once you’ve updated the remote URL, try pushing your changes again:
bash
git push origin main

If you still encounter issues, it might be related to your local Git configuration. Make sure your credentials are correct — for HTTPS, check your username and password or personal access token. For SSH, ensure your SSH keys are correctly added to GitHub.

By confirming your access rights, updating your remote URL to a writable repository, and verifying your credentials, you should be able to push your code without encountering the “Repository is Read-Only” error anymore. If problems persist, contact the repository owner for further assistance.