Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

How exactly use IndexEntry

Open
#1,051 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, python
Domain
devtools

Research direction

Start with the IndexEntry example and the repo.index.add/write calls shown in the issue, then compare the index state with the displayed git status output. Document or verify the correct way to stage the created blob, with completion shown by git status reporting only the intended staged file.

Written by the indexing model from the issue text.

Description

Trying adding file with IndexEntry, this my way:

id  = repo.create_blob('foo bar')
entry = pygit2.IndexEntry('zend2.txt', id, pygit2.GIT_FILEMODE_BLOB_EXECUTABLE)

repo.index.add(entry)
repo.index.write()

But with git status return this.

On branch master
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        new file:   zend2.txt

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        deleted:    zend2.txt

How to add that blob to staged index.

Dominant language
Python
Stars
1.7k
Forks
408
Avg merge
2d 57m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libgit2/pygit2

All issues in libgit2/pygit2

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.