Added Docker build, updated libgit2 and added some custom commands

[rraab-dev]

Hello,

nice work on here. Since I use this code in a project as well and needed to add some functionality / commands. I hope the changes made could also be useful for others.

Added Dockerfile for Docker build:

• Dockerfile and docker_cleanup_and_build.sh.
• Added documentation for Docker build.

Updated libgit2 from version 1.7.1 to 1.8.1:

• Removed git_error_clear() call in examples/checkout.c cause method had been removed.

Added new commands:

• examples/branch.c: List local and remote branches. Delete local branches.
• examples/log-last-commit-of-branch.c: Log info about latest commit of a branch.
• examples/rebase.c: Interactive rebase functionality.

Changed commands:

• examples/push.c: Does have an optional parameter --force for force pushing. (Needed after a rebase.)
• examples/fetch.c: Does now --prune by default.
• examples/init.c: Change default branch to main.
• examples/diff.c: Added --full-file-content option which allows printing old_file and new_file content if available.

Others

• Added HTTP basic auth for authentication with password or pat.
• Added method writeArrayToMemory manually to post.js cause it was not found.

Eager to hear your feedback.

Regards
Rafael

[kkoomen]

Would be awesome if you could also implement support for --depth 1 :D

[rraab-dev]

Would be awesome if you could also implement support for --depth 1 :D

I implemented in examples/log-last-commit-of-branch.c a log with depth 1 for a branch. You can pass a branch name as parameter and log the latest commit of it.

Usage:
lg2 log-last-commit-of-branch {branch}

https://github.com/petersalomonsen/wasm-git/pull/99/files#diff-ac905392268f36588a7045a34d8ca4d3b31ea46e252db801ce9e663eee6e166c

If you want to clone a repository / fetch with depth --1 you have to change the fetch_opts inside the git_clone_options when a clone is performed.

[petersalomonsen]

@rraab-dev thanks for your contribution.

Upgrading of libgit2 is always useful, thanks for going through that !

Adding of new commands is great. Are any of these also already in the libgit2 codebase? And for the changed commands, are these changes also according to standard command line git ( which I've attempted to maintain until now ).

I also enabled running the tests, and I see failures. I haven't looked deeper into why. Would you take a look to see if you can find the reason for the failures?

Also tests for your new commands and enhancements of existing commands would be great. This way we can ensure that future contributions will not cause breaking changes to the contributions you've made here. I would also appreciate if your changes does not require any existing tests to be changed, as that would mean a breaking change for existing apps that use wasm-git.