Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 624301
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T19:11:08+00:00 2026-05-13T19:11:08+00:00

On my local git repo I’ve got many commits, which include ‘secret’ connection strings

  • 0

On my local git repo I’ve got many commits, which include ‘secret’ connection strings 🙂

I don’t want this history on github when I push it there.

Essentially I want to push everything I have, but want to get rid of a whole lot of history.

Perhaps I would be better running in a branch for all my dev, then just merging back to master before committing… then the history for master will just be the commit I want.

I’ve tried running rebase:

git rebase –i HEAD~3

That went back 3 commits, and then I could delete a commit.

However ran into auto cherry-pick failed, and it got quite complex.

Any thoughts greatly appreciated… no big deal to can the history and start again if this gets too hard 🙂

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T19:11:09+00:00Added an answer on May 13, 2026 at 7:11 pm

    You can branch your current work, rewind the master, then cherry-pick the latest commit back to the master:

    git branch secret
    git reset --hard HEAD~3
    git cherry-pick secret
    

    In pictures,

        A--B--C--D--E (master)
    

    after git branch secret:

        A--B--C--D--E (master, secret)
    

    after git reset --hard HEAD~3:

        A--B (master)
            \
             C--D--E (secret)
    

    after git cherry-pick secret:

        A--B--E' (master)
            \
             C--D--E (secret)
    

    Finally, if you git checkout secret; git rebase master, you can get:

        A--B--E' (master)
               \
                C--D (secret)
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.