Скачать или смотреть How to Remove .gitignored Files Using Recursive Patterns in Git

A comprehensive guide on how to effectively remove .gitignored files in Git, especially when working with recursive patterns like `foo/**`. Learn the best commands and workarounds to manage your repository efficiently.
---
This video is based on the question https://stackoverflow.com/q/65353248/ asked by the user 'Stefan Dragnev' ( https://stackoverflow.com/u/243103/ ) and on the answer https://stackoverflow.com/a/65386560/ provided by the user 'jthill' ( https://stackoverflow.com/u/1290731/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to remove files that are .gitignored with a recursive .../** pattern?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Remove .gitignored Files Using Recursive Patterns in Git

When working with Git, managing ignored files efficiently can sometimes lead to a frustrating experience, especially when using recursive patterns in your .gitignore file. Have you ever encountered a situation where you want to remove files that are listed as ignored in your Git repository, but your commands aren't behaving as expected? Let’s explore this common issue and provide a solution to help you navigate through it.

The Problem

Imagine you have initialized a new Git repository, added some files, and specified certain patterns in your .gitignore file — for example, foo/**. You might expect that running a clean command would effectively remove any files that fall under this pattern.

Here’s an example setup that demonstrates the problem:

[[See Video to Reveal this Text or Code Snippet]]

When you run git status --ignored, you see:

[[See Video to Reveal this Text or Code Snippet]]

However, if you then run the command:

[[See Video to Reveal this Text or Code Snippet]]

you might notice that the file foo/bar still remains untouched. This can be puzzling, as changing your .gitignore rule to just foo/ would delete the foo/ folder as expected.

Understanding the Issue

This behavior appears to stem from how Git handles recursive ignore patterns. Specifically, it seems the -X option for git clean doesn't fully recurse into directories that are wholly ignored. Therefore, files remaining in these directories may not be removed as anticipated.

Common Behaviors:

Just foo/: Removing this directory works as intended.

foo/**: Leads to unexpected results where files inside the folder remain.

A Simple Solution

To effectively remove these .gitignored files, including those in recursively ignored directories, you can use a workaround that utilizes a combination of Git commands and shell utilities.

Step-by-Step Workaround

Use git ls-files Command:

First, you will execute the following command to list files ignored by Git:

[[See Video to Reveal this Text or Code Snippet]]

Explanation:

git ls-files -oi --exclude-standard: Lists ignored files.

-z | xargs -0 rm: Safely removes files by ensuring proper handling of file names.

Clean Empty Directories:

After removing the unwanted files, you may want to clean up any now-empty directories. You can achieve this using:

[[See Video to Reveal this Text or Code Snippet]]

This command will search for empty directories and delete them, ensuring your project folder remains tidy.

Additional Insights on Directory Handling

On Linux, when trying commands under various configurations, you may notice differing behaviors. For example:

[[See Video to Reveal this Text or Code Snippet]]

By testing with git ls-files -oc|git check-ignore --stdin and git clean -nX, you can see how ignored files and directories interact differently based on tracked content.

Conclusion

In summary, while dealing with .gitignored files using recursive patterns can prove tricky, applying the workaround with git ls-files and xargs provides a straightforward solution. Moreover, keeping your directories clean with find ensures that your repository remains organized and manageable.

That's it! With these insights and commands, you should now be able to easily manage and remove .gitignored files within your Git repository. Happy coding!