dulwich/docs/tutorial/2-change-file.txt

Changing a File and Commit it
=============================

Now we have a first commit, the next one will show a difference.

As seen in the introduction, it's about making a path in a tree point to a
new blob. The old blob will remain to compute the diff. The tree is altered
and the new commit'task is to point to this new version.

In the following examples, we assume we still have the ``repo`` and ``tree``
object from the previous chapter.

Let's first build the blob::

  >>> spam = Blob.from_string("My new file content\n")
  >>> spam.id
  '16ee2682887a962f854ebd25a61db16ef4efe49f'

An alternative is to alter the previously constructed blob object::

  >>> blob.data = "My new file content\n"
  >>> blob.id
  '16ee2682887a962f854ebd25a61db16ef4efe49f'

In any case, update the blob id known as "spam". You also have the
opportunity of changing its mode::

  >>> tree["spam"] = (0100644, spam.id)

Now let's record the change::

  >>> c2 = Commit()
  >>> c2.tree = tree.id
  >>> c2.parents = [commit.id]
  >>> c2.author = c2.committer = author
  >>> c2.commit_time = c2.author_time = int(time())
  >>> c2.commit_timezone = c2.author_timezone = tz
  >>> c2.encoding = "UTF-8"
  >>> c2.message = 'Changing "spam"'

In this new commit we record the changed tree id, and most important, the
previous commit as the parent. Parents are actually a list because a commit
may happen to have several parents after merging branches.

Remain to record this whole new family::

  >>> object_store.add_object(spam)
  >>> object_store.add_object(tree)
  >>> object_store.add_object(c2)

You can already ask git to introspect this commit using ``git show`` and the
value of ``commit.id`` as an argument. You'll see the difference will the
previous blob recorded as "spam".

You won't see it using git log because the head is still the previous
commit. It's easy to remedy::

  >>> repo.refs['refs/heads/master'] = c2.id

Now all git tools will work as expected. Though don't forget that Dulwich is
still open!