如果没有创建分支并在新分支上做一堆时髦的工作,是否有可能在提交到本地存储库后将单个提交分解为几个不同的提交？

预期行为

我编辑了 file1，提交并执行了此操作

$ git push

NOTICE: Only authorized blah blah blah...

Counting objects: 7, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 676 bytes | 0 bytes/s, done.
Total 7 (delta 4), reused 0 (delta 0)
To ssh://me@server:/opt/git/fooBar.git
   28ad03d..73ae492  master -> master
$

问题

然后我在同一个项目中编辑了 file2，提交并执行了以下操作：

$ git push

NOTICE: Only authorized blah blah blah...

Counting objects: 10, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (8/8), …

我想知道当它推动变化时git正在做什么,以及为什么它似乎偶尔会推动更多的数据而不是我所做的更改.我对两个增加了大约100行代码的文件进行了一些更改 - 不到2k的文本,我想.

当我将数据推送到原点时,git将其转换为超过47mb的数据:

git push -u origin foo
Counting objects: 9195, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6624/6624), done.
Writing objects: 100% (9195/9195), 47.08 MiB | 1.15 MiB/s, done.
Total 9195 (delta 5411), reused 6059 (delta 2357)
remote: Analyzing objects... (9195/9195) (50599 ms)
remote: Storing packfile... done (5560 ms)
remote: Storing index... done (15597 ms)
To <<redacted>>
 * [new branch]      foo -> foo
Branch foo set up to track remote branch foo from origin. …

我尝试将一些文件推送到Github，总大小只有22.2M。我不知道为什么它在总行之后卡住了。我读过Git 推送在推送到 Github 时挂起？并尝试了每个答案，但它根本不起作用。效果好吗？我有什么方法可以加速这个过程吗？

Counting objects: 203, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (176/176), done.
Writing objects: 100% (203/203), 22.12 MiB | 15.70 MiB/s, done.
Total 203 (delta 23), reused 0 (delta 0)