blocks|key|4202853|text|只需将图像添加到gitignore。您不需要将它们存储在repo中，对吧？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4202854|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just add images to gitignore. You do not need to store them in repo, right?

blocks|key|2737311|text|对于要删除的每个文件，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2737312|git+update-index+--assume-unchanged+<file>|code-block|syntax|javascript|2737313|这应该会阻止Git要求您提交删除。|2737314|话虽如此，也许更好的解决方案是使用SFTP，并将权限设置为不允许在上载后删除或修改文件。|2737315|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For each file to be deleted, do this:

<pre><code>git update-index --assume-unchanged &lt;file&gt;
</code></pre>

This should stop Git from asking you to commit the deletion.

That being said, perhaps a better solution would be to use SFTP with permissions set to disallow deleting or modifying files once uploaded.

blocks|key|4202923|text|(编辑:将有效负载打包为自包含脚本)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4202924|您正在寻找一个几乎只具有状态的本地存储库，该存储库跟踪您所创建的所有内容的存在，但只保留最新内容的内容(在将所有内容推到上游之后)。假设你从未重用过路径名，下面是一个惯例：|4202925|一次性设置：|offset|length|style|BOLD|4202926|创建并推送一个everything分支，用于跟踪到目前为止获得的每个图像。在此基础上创建一个(仅限本地的)+worktree分支。|CODE|4202927|git+checkout+-b+everything+++++#+this+will+be+the+branch+you+push
git+push+origin+everything+++++#+.
git+checkout+-b+worktree+++++++#+you'll+stay+on+this+branch|code-block|syntax|javascript|4202928|(几乎)就像您不想做任何特别的事情一样工作：|4202929|上游需要保留的所有内容都在everything分支上，并且您已经检查了worktree。从工作树中删除已处理完毕的图像，在其中生成需要推送的新图像，然后提交新的工作树状态：|4202930|#+work+work:
rm+-r+anything/+you\'re/+done+with
create+new+images
git+add+-A+.++#+good+gitignore+patterns+make+life+easy
git+commit|4202931|要执行请求的工作，请运行|4202932|merge-push-and-cleanup+++#+the+script+below|4202933|在此之后，所有内容都存储在上游，没有多余的东西留在本地，您可以进行更多的工作。|4202934|4202935|+merge-push-and-cleanup+脚本：|4202936|#!/bin/sh
#+Git+can+do+"index-only"+merges+when+the+content+doesn't+need+to+be+examined,
#+you+can+casually+create+sideband+indexes,+and+`git+commit-tree`+works+on+any+
#+tree+in+the+repo.

++(
#+%5E+subshell+to+keep+G_I_F+export+local
++export+GIT_INDEX_FILE=.git/sideband-index

++#+make+a+merged+index+that+includes+everything+from+both+branches,+by
++#+starting+from+an+empty+merge+base+so+all+files+show+up+as+additions.

++git+read-tree+-im+$(git+mktree+</dev/null)+worktree+everything

++#+commit+to+the+`everything`+branch+straight+from+the+constructed+index,
++#+reusing+the+commit+message+from+`worktree`

++git+cat-file+-p+worktree+%7C+sed+1,/%5E$/d+\
++%7C+git+commit-tree+-p+everything+-p+worktree+$(git+write-tree+--missing-ok)+\
++%7C+xargs+git+update-ref+refs/heads/everything
)

git+push+origin+everything

#+preserve+the+branch+metadata+and,+just+for+safety,+your+latest+images
#+by+packing+it+all+up:

mkdir+-p+.git/preserved/pack
rm+-f+.git/preserved/pack/*
(
++git+rev-list+worktree+everything
++git+rev-parse+worktree%5E{tree}+everything%5E{tree}
++git+ls-tree+-rt+worktree+%7C+awk+'{+print+$3+}'
++git+ls-tree+-rt+everything+%7C+awk+'$2+!=+"blob"+{+print+$3+}'
)+\
%7C+git+pack-objects+.git/preserved/pack/pack

#+now+for+the+fun+one:
rm+-rf+.git/objects/*+++#+!!!

#+put+the+preserved+stuff+back:
mv+.git/preserved/pack+.git/objects|4202937|entityMap^0|0|0|0|6|0|7|A|1I|8|0|0|0|M|0|D|A|Z|8|0|0|0|0|0|0|1|M|O|3|1|M|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1F|8|@$F|1G|G|1H|H|L]|$F|1I|G|1J|H|L]]|9|@]|A|$]]|$1|M|3|N|5|O|7|1K|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|1L|8|@$F|1M|G|1N|H|I]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1O|8|@$F|1P|G|1Q|H|L]|$F|1R|G|1S|H|L]]|9|@]|A|$]]|$1|V|3|W|5|O|7|1T|8|@]|9|@]|A|$P|Q]]|$1|X|3|Y|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Z|3|10|5|O|7|1V|8|@]|9|@]|A|$P|Q]]|$1|11|3|12|5|6|7|1W|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1Y|8|@$F|1Z|G|20|H|I]|$F|21|G|22|H|I]|$F|23|G|24|H|L]]|9|@]|A|$]]|$1|16|3|17|5|O|7|25|8|@]|9|@]|A|$P|Q]]|$1|18|3|-4|5|6|7|26|8|@]|9|@]|A|$]]]|19|$]]

(edit: package up the payload as a self-contained script)

You're after a nearly status-only local repository that tracks the existence of everything you've ever created but keeps the contents of only the most recent stuff (after pushing everything upstream). Presuming you never reuse a pathname, here's the ritual:

One-time setup:

Create and push an <code>everything</code> branch that tracks every image you've got so far. Base a (local-only) <code>worktree</code> branch off that.

<pre><code>git checkout -b everything # this will be the branch you push
git push origin everything # .
git checkout -b worktree # you'll stay on this branch
</code></pre>

Work (almost) as if you didn't want to do anything special:

Everything that needs preserving upstream is on the <code>everything</code> branch, and you've got <code>worktree</code> checked out. Remove images you're done with from the worktree, make new images there that need pushing, and commit the new worktree state:

<pre><code># work work:
rm -r anything/ you\'re/ done with
create new images
git add -A . # good gitignore patterns make life easy
git commit
</code></pre>

To do the requested work, run

<pre><code>merge-push-and-cleanup # the script below
</code></pre>

After which everything's stored upstream, nothing redundant remains locally, and you're ready for more work.

<hr>

The <code>merge-push-and-cleanup</code> script:

<pre><code>#!/bin/sh
# Git can do "index-only" merges when the content doesn't need to be examined,
# you can casually create sideband indexes, and `git commit-tree` works on any 
# tree in the repo.

 (
# ^ subshell to keep G_I_F export local
 export GIT_INDEX_FILE=.git/sideband-index

 # make a merged index that includes everything from both branches, by
 # starting from an empty merge base so all files show up as additions.

 git read-tree -im $(git mktree &lt;/dev/null) worktree everything

 # commit to the `everything` branch straight from the constructed index,
 # reusing the commit message from `worktree`

 git cat-file -p worktree | sed 1,/^$/d \
 | git commit-tree -p everything -p worktree $(git write-tree --missing-ok) \
 | xargs git update-ref refs/heads/everything
)

git push origin everything

# preserve the branch metadata and, just for safety, your latest images
# by packing it all up:

mkdir -p .git/preserved/pack
rm -f .git/preserved/pack/*
(
 git rev-list worktree everything
 git rev-parse worktree^{tree} everything^{tree}
 git ls-tree -rt worktree | awk '{ print $3 }'
 git ls-tree -rt everything | awk '$2 != "blob" { print $3 }'
) \
| git pack-objects .git/preserved/pack/pack

# now for the fun one:
rm -rf .git/objects/* # !!!

# put the preserved stuff back:
mv .git/preserved/pack .git/objects
</code></pre>

blocks|key|421836|text|使用Skip-Worktree位|type|unstyled|depth|inlineStyleRanges|entityRanges|data|421837|git-update-index(1)命令提供了一些处理此问题的方法。基于这样的假设，您希望在从工作树中删除blobs时将其保留在历史记录中，您可以使用以下方法：|offset|length|421838|git+add+--all
git+commit+--message="Add+new+assets+to+repository."
git+update-index+update-index+--skip-worktree+<files+...>
rm+<files+...>|code-block|syntax|javascript|421839|请注意，最后一行不是Git命令，因为在将文件存储到索引之后，您将从shell的工作树中删除这些文件。不要错误地使用git+rm，因为它对索引进行操作。|style|CODE|421840|列出特殊的Bits和仅索引文件|421841|要查看使用跳过工作树标记的文件，请执行以下操作：|421842|git+ls-files+-v+%7C+awk+-v+IGNORECASE=1+'$1+~+/s/+{print}'|421843|您还可以使用git-ls-files(1)在索引中查找已从工作树中删除的文件。|421844|entityMap|0|LINK|mutability|MUTABLE|url|https://www.kernel.org/pub/software/scm/git/docs/git-update-index.html|1|https://www.kernel.org/pub/software/scm/git/docs/git-ls-files.html^0|0|0|J|0|0|0|1L|6|0|0|0|0|6|F|1|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|H|7|1B|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1C|8|@$D|1D|E|1E|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1G|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|1H|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1I|8|@]|9|@$D|1J|E|1K|1|1L]]|A|$]]|$1|W|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|15]]]]

<h2>Use the Skip-Worktree Bit</h2>

The <a href="https://www.kernel.org/pub/software/scm/git/docs/git-update-index.html" rel="nofollow">git-update-index(1)</a> command provides some ways of dealing with this. Based on the assumption that you want to keep the blobs in your history while deleting them from your working tree, you could use the following:

<pre><code>git add --all
git commit --message="Add new assets to repository."
git update-index update-index --skip-worktree &lt;files ...&gt;
rm &lt;files ...&gt;
</code></pre>

Note that the last line isn't a Git command because you're removing the files from the working tree in the shell after you've stored them in the index. Don't use <code>git rm</code> by mistake, because it operates on the index.

<h2>Listing Your Special Bits and Index-Only Files</h2>

To see the files you've marked with the skip-worktree bit:

<pre><code>git ls-files -v | awk -v IGNORECASE=1 '$1 ~ /s/ {print}'
</code></pre>

You can also use <a href="https://www.kernel.org/pub/software/scm/git/docs/git-ls-files.html" rel="nofollow">git-ls-files(1)</a> to find files in the index that have been removed from your working tree.

We have a situation where were are using git to stash myriad scans (images) and do not wish to preserve them on the local machine once set on up; however, git is seeing each local deletion (following this process) as something to be committed up to the repo, and we want that not to happen. Any ideas on how to commit only the additional files and never any deletions?

How to NOT commit locally deleted files to git

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们有这样一种情况，我们使用git来隐藏无数的扫描(图像)，并且不希望在本地机器上保存它们；然而，git将每个本地删除(遵循此过程)视为要提交到repo，我们不希望发生这种情况。关于如何只提交额外的文件而不删除文件，有什么建议吗？

问如何不将本地删除的文件提交到git
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何不将本地删除的文件提交到gitEN