How to disable viewing or delete a commit ON SITE or in GitHub Desktop ?

[flyupunity]

Select Topic Area

Question

Body

I wanted to publish a repository, but the commits have my personal information in them, how do I disable picture preview or delete a commit ON SITE or in GitHub Desktop ?

[codewithmuh]

If you want to publish a repository on GitHub, but the commits in the repository contain your personal information, you have a couple of options to address this issue. One option is to disable picture previews for the sensitive commits, and another option is to remove the sensitive commits entirely.

Disable Picture Preview for Sensitive Commits:
GitHub doesn't have a built-in feature to disable picture previews for specific commits. However, you can follow these steps to remove the images from the commits and overwrite them:

a. Clone the Repository:
Using GitHub Desktop, clone the repository to your local machine.

b. Remove the Images:
Manually go through the sensitive commits and remove any images from them. To do this, you can either rewrite the commit history or use git rebase -i to edit individual commits.

c. Force Push the Changes:
After removing the images from the commits, you'll need to force push the changes to your GitHub repository. Keep in mind that force pushing rewrites the repository's history, so be cautious when using it.

Delete the Sensitive Commits:
If you decide to delete the sensitive commits entirely, follow these steps:

a. Clone the Repository:
Clone the repository to your local machine using GitHub Desktop.

b. Use Interactive Rebase:
Open a terminal or command prompt in the repository directory and run the following command to perform an interactive rebase:

git rebase -i HEAD~n
Replace n with the number of commits you want to edit from the most recent commit.

c. Delete the Commits:
An editor will open, showing the list of commits you selected. Delete the lines representing the commits you want to remove. Save and close the editor.

d. Force Push the Changes:
After removing the unwanted commits, you'll need to force push the changes to your GitHub repository:

git push origin branch-name --force
Replace branch-name with the name of the branch you are working on.

Important Note:
Be cautious when rewriting commit history or force pushing, as it can affect collaborators and users who have already cloned the repository. It's a good practice to communicate with your collaborators and inform them about any history rewriting you intend to do.

Before proceeding with any of the above steps, make sure to create a backup of your repository or work on a separate branch to avoid data loss.

[John4650-hub]

Thank you

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬