libgit2 / libgit2.github.io Goto Github PK

Visit https://libgit2.org/docs/guides/101-samples/#remotes_callbacks. In this text:

For an example of the credentials callback in action, check out the network example, or the built-in credential helpers.

"the network example" links to https://github.com/libgit2/libgit2/blob/master/examples/network/common.c which is a 404. It's not obvious to me which file it should link to.

The http://libgit2.github.com/libgit2/ redirects back to https://libgit2.org/ - the js console also says:

Failed to load resource: the server responded with a status of 404 () for resource https://use.typekit.com/jsq2fql.js

git is GPLv2 https://github.com/git/git/blob/master/COPYING is this project truly an independent implementation that has not been based on the viewing of any git code?

causing many operations, such as git_rebase_init (which results in calls to git_submodule_lookup several times for each submodule) to be O(N^2).

On a 3.1Ghz MBP with SSD, for example, a single call to git_submodule_lookup in a repository with 4,000 submodules takes over 20ms.

I am very happy to work on this myself and submit a patch, but I wanted to open a discussion and get advice on how to proceed. One suggestion: allow an option to configure a repository to cache this information on first submodule access.

Hi guys, sorry if that's not the correct place for asking this question, but I'm literally desparate. I had my program working perfectly using git_status_list_new, that is the status object was properly initialized and I could do further processing of it.
Yesterday I've run my program and from nowhere, suddenly git_status_list_new cannot initialize status object, that is, status object is nullptr. I didn't touch the code. Don't know what have happened. I wonder if anyone of you happen to come across similar situation?
Any help really appreciated.
Thank you.

Just got this notification after a new build:

The page build completed successfully, but returned the following warning:

You are currently using the 'redcarpet' Markdown engine, which will not be supported on GitHub Pages after May 1st. At that time, your site will use 'kramdown' for markdown rendering instead. To suppress this warning, remove the 'markdown' setting in your site's '_config.yml' file and confirm your site renders as expected. For more information, see https://help.github.com/articles/updating-your-markdown-processor-to-kramdown.

GitHub Pages was recently upgraded to Jekyll 3.0. It may help to confirm you're using the correct dependencies:

https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

For information on troubleshooting Jekyll see:

https://help.github.com/articles/troubleshooting-jekyll-builds

If you have any questions you can contact us by replying to this email.

I had a quick peek at the config and unfortunately there's a number of redcarpet extensions specified (which I'm not familiar with):

markdown: kramdown
redcarpet:
  extensions: ["no_intra_emphasis", "fenced_code_blocks", "autolink", "tables", "with_toc_data"]
exclude: ['Readme.md']

Opening this so we don't forget to do something about it before May 1st.

The remotes callbacks sample uses git_transfer_progress and git_fetch_options::progress which have been removed.

The commit 2424c84 change some link libgit2.github.com as libgit2.org.
But the new url of the reference API's part: https://libgit2.org/libgit2/ return a 404 File Not Found.
The older url https://libgit2.github.com/libgit2/ still working.

Given a local branch ref like refs/heads/master and a remote branch ref refs/remotes/origin/foo I cannot find a way with the current api to produce a valid refspec that git_remote_push accepts.

Just concatenating them like so wont work: refs/heads/master:refs/remotes/origin/foo

I have to manually "rename" the remote branch ref with naive string ops to look like refs/heads/foo to produce a valid refspec for pushing to a remote name with a different name.

Looking like this: refs/heads/master:refs/heads/foo

Did I overlook something or how else do I get from a remote branch name to a refspec name that git_remote_push will accept? Or is there simply no API to convert?

Hello,
I am starting to learn the libgit2 API and in the first example I wanted to try I stumbled upon git_indexer_progress: https://libgit2.org/docs/guides/101-samples/#repositories_clone_progress.
Unfortunately, this does not appear anywhere in the reference: https://libgit2.org/libgit2/#HEAD/search/git_transfer_progress.
Further investigation showed that it is simply because it is a deprecated name of git_indexer_progress.

So, I will definitely do a PR for this particular instance, but it would be nice to be able to catch all such symbols automatically if possible.

Do you think there would be a reliable way to do so, or we should try to parse the "deprecated" header ?

Hi,

it looks like the link to libqgit2 is broken

quickgit.kde.org results in an DNS_PROBE_FINISHED_NXDOMAIN error on chrome.

rebase.zip

I am using nodegit, but I do not think the problem is in that library as their Rebase.init and Rebase.next functions appear to be passthroughs.

If you attempt to rebase onto a branch where there would be a conflict in a submodule, the very first call to get_rebase_next fails with the message: "uncommitted change would be overwritten by merge". I imagine the problem has to do with the state of the submodule itself (which is not altered by the rebase) being taken as dirty.

I am able to work around this problem (after which I encounter other problems) by synchronizing (via git_submodule_update) the submodule(s) after calling git_rebase_init.

For an example, unzip the attached setup.sh and test.js in the same directory and run $ bash setup.sh. This script will set up the situation such that a base1 repo is ready to rebase its master branch onto origin/master with a conflict in the submodule x. It then executes test.js with node to attempt to start the rebase operation.

http://hackage.haskell.org/package/hlibgit2

Hi there,

it looks like, that choobie is no longer supporting the actual php-git project.
Therefore I opened an issue to inform other that i startet an own project to add PHP 7 support.

The idea is to change the address of the website to this project.
https://github.com/garvins/php-git.git

👋 I stumbled over https://libgit2.org/security/ today, and noticed that it hasn't been updated since the end of 2018. However newer fixes such as libgit2/libgit2#5331 don't seem to be listed on the website.

Is this still something worth keeping up to date?

running

int main(int argc, char **av)
{
git_repository *repo = NULL;
const char *path = "/home/example/utils/escape"; // existing empty directory with write permissions
const char *url="https://github.com/dpnishant/jsprime.git";
return git_clone(&repo, url, path, NULL);
}

triggers

assertion "git_atomic_get(&git__n_inits) > 0" failed: file "libgit2/src/global.c", line 384, function: git__global_state
Aborted (core dumped)

We ran into a problem with git2-15e1193.DLL as we change our test environment to Windows Server 2016.
We changed back to 2012 R2 and it runs without issues.

Unhandled exception at 0x00007FFA745E3882 (git2-15e1193.DLL) in vstest.executionengine.exe.7648.dmp: 0xC0000005: Access violation reading location 0x000000000000000C.
If there is a handler for this exception, the program may be safely continued.

Call Stack:

git2-15e1193.DLL!00007ffa8c933882() Unknown
git2-15e1193.DLL!00007ffa8c9c87fa() Unknown
ntdll.dll!LdrpCallInitRoutine() Unknown
ntdll.dll!LdrShutdownThread() Unknown
ntdll.dll!RtlExitUserThread�() Unknown
kernel32.dll!BaseThreadInitThunk�() Unknown
ntdll.dll!RtlUserThreadStart�() Unknown

GitHub Pages will stop redirecting Pages sites from *.github.com after April 15, 2021: https://github.blog/changelog/2021-01-29-github-pages-will-stop-redirecting-pages-sites-from-github-com-after-april-15-2021/

Hello, If I’m correct, libgit2 isn’t an official GitHub product isn’t it ?
In that case, how are you doing in order to get a website under a subdomain of github.com instead of github.io ?

Hi,

I've recently posted a tutorial on my blog about how to traverse a git repository using libgit2 and C++ and I was wondering if would be a good idea to add it (after some editing) to the annotated examples.

My idea is to copy the code explained, replace C++ code with C and use the same formatting used in the Repository Initialization example.

Please let me know if this is ok before I do it and submit it as pull request.

libgit2.org lists nodegit as a Node.js binding of libgit2. However, the last stable release of nodegit is from 2020, there are no prebuilt binaries for any supported Node.js version anymore (only Node 16), and it depends on the long-deprecated "request" library that has security vulnerabilities. There are several issues asking about the project state without replies from the maintainers.

Developers looking for a library to use Git in Node.js will likely just get frustrated when they start with using Node.js.

Hi,

I'm sorry if this seems like a common question, but I can't find any current answer to this. I am using libgit2 and would like to use Git LFS. I thought that creating the corresponding hooks would be enough, but that doesn't make it work

So in short:

1. Is Git LFS supported?
2. Are there any resources to implement it?

Thank you very much!

Wanted to do the equivalent of the git repack command, and I'm stuck on how to do it.

I definitely need an example. By the way, it would be usefull to include it on the site.

I need build in libgit2 by AndroidStudio.
But, below happened on compile error.
Need modify in-line code.
/src/common.h LINE 97

/* Work around C90-conformance issues */
#if !defined(__STDC_VERSION__) || (__STDC_VERSION__ < 199901L)
# if defined(_MSC_VER)
#  define inline __inline
# elif defined(__GNUC__)
#  define inline __inline__
# else
#  define inline
# endif
#endif

# include <arpa/inet.h>

libgit2 front page link:
https://projects.kde.org/projects/playground/libs/libqgit2/
redirects to:
https://quickgit.kde.org/?p=.git

working link, I assume is: https://quickgit.kde.org/?p=libqgit2.git