libgit2 / libgit2/pygit2

Unable to push to remote after committing files

Open
#1,053 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I am committing some files using pygit2 and want to push to remote branch.
This is what i am doing:

        repo = pygit2.Repository(build_dir)
        branch = repo.lookup_branch(local_branch)
        repo.checkout(branch)
        for fl in files:
           repo.index.add(fl)
        repo.index.write()
        message = f"Commiting files {files}"
        tree = repo.index.write_tree()
        parent, ref = repo.resolve_refish(refish=repo.head.name)
        author = pygit2.Signature("user", "email")
        commiter = pygit2.Signature("user", "email")

        repo.create_commit(
            ref.name,
            author,
            commiter,
            message,
            tree,
            [parent.oid],
        )



        remote = repo.remotes["origin"]
        callbacks = pygit2.RemoteCallbacks(pygit2.UserPass("username", GITHUB_PERSONAL_ACCESS_TOKEN))
        remote.push(['refs/heads/master'],callbacks=callbacks)

And i get an error:
_pygit2.GitError: unsupported URL protocol

I cannot find any documentation or any clarity on whats going on here.

Any help will be much appreciated.

thanks

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.

Research direction

Start by inspecting the repository's configured origin URL and the remote.push call, then verify how the provided RemoteCallbacks and UserPass credentials are used. Reproduce the unsupported URL protocol error with the shown pygit2 code and compare the remote configuration with supported protocols. Done means identifying the configuration or callback issue and documenting a verified successful push.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.