Take non-materialized .gitignore into account in sparse working copies - #10188
twistedfall wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
There was a problem hiding this comment.
The following commits do not follow our format for subject lines:
- 4a313df: Take non-materialized .gitignore into account in sparse working copies
Commits should have a subject line following the format <topic>: <description>. Please review the commit guidelines for more information.
4a313df to
d088312
Compare
All commits are now correctly formatted. Thank you for your contribution!
d088312 to
7e63f4f
Compare
There was a problem hiding this comment.
The following commits do not follow our format for subject lines:
- 7e63f4f: Take .gitignore into account in sparse copies
Commits should have a subject line following the format <topic>: <description>. Please review the commit guidelines for more information.
7e63f4f to
f0fe2dc
Compare
All commits are now correctly formatted. Thank you for your contribution!
When .gitignore is sparsed-away it stops affecting the file tracking status and files that were supposed to be ignored become tracked as soon as .gitignore disappears. This change allows us to look up the .gitignore files in the repository and take them into account.
Fixes #2289
Checklist
If applicable:
CHANGELOG.mdREADME.md,docs/,demos/)cli/src/config-schema.json)how it works, how it's organized), including any code drafted by an LLM.
an eye towards deleting anything that is irrelevant, clarifying anything
that is confusing, and adding details that are relevant. This includes,
for example, commit descriptions, PR descriptions, and code comments.