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

  • Home
  • SEARCH
  • 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 8890249
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T22:27:29+00:00 2026-06-14T22:27:29+00:00

I have a config file which was committed earlier by mistake. I added it

  • 0

I have a config file which was committed earlier by mistake. I added it to .gitignore and also did a git update-index --assume-unchanged, but when I do a git checkout -- ., it reverts it back to an older, committed version. How can I ignore it completely?

  • 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-06-14T22:27:31+00:00Added an answer on June 14, 2026 at 10:27 pm

    If a file is already being tracked (has been committed, and specifically exists in your HEAD commit), it cannot be ignored via .gitignore. If you want to prevent it showing up in future checkouts, you need to git rm --cached <file>; git commit -m "stop tracking <file>". If also removing the copy in your working directory is acceptable, you can drop the --cached option to git rm.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am using php and mysql. I have a Database config file (db-config.php) which
I have a python class which reads a config file using ConfigParser: Config file:
I have created a library which reads the app.config file and gets the type
I have a Web application (with a Web.config file), which will move through the
In my app, I have a simple ASCII file which stores some config info
I have an app config file which declares globals using DEFINE: define('BASE_DOMAIN', 'localhost/...'); define('BASE_URL',
I have a proxy config file which has the following line: Allow 212.21.3.44 I'd
I have a config file which includes some factors I want to use for
I have a config file in which I have keys and values, like this:
I have a config file which is mainly used in shell scripts, and therefore

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.