| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
hashes
|
| |
|
|
|
|
|
|
|
|
|
| |
Before this, go-git would prematurely bail out of extensions processing
when an unknown extension was encountered. This had two issues:
1. It did not account for mandatory (lower case header) extensions
2. It did not properly update the calculated hash, leading to an
"invalid checksum" error.
|
|
|
|
|
|
|
|
|
| |
Before this, go-git was relying on the peeked header to not include a valid
4 char string header. While doing this, it did not differentiate between
the errournously read final hash and an unknown extension.
This made it impossible to properly skip unknown optional extensions while
detecting EOF early enough.
|
|\
| |
| |
| |
| | |
go-git/dependabot/go_modules/golang.org/x/net-0.24.0
build: bump golang.org/x/net from 0.23.0 to 0.24.0
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.23.0 to 0.24.0.
- [Commits](https://github.com/golang/net/compare/v0.23.0...v0.24.0)
---
updated-dependencies:
- dependency-name: golang.org/x/net
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| |
| |
| | |
go-git/dependabot/go_modules/golang.org/x/net-0.23.0
build: bump golang.org/x/net from 0.22.0 to 0.23.0
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.22.0 to 0.23.0.
- [Commits](https://github.com/golang/net/compare/v0.22.0...v0.23.0)
---
updated-dependencies:
- dependency-name: golang.org/x/net
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| |
| |
| | |
go-git/dependabot/go_modules/cli/go-git/github.com/go-git/go-git/v5-5.12.0
build: bump github.com/go-git/go-git/v5 from 5.11.0 to 5.12.0 in /cli/go-git
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [github.com/go-git/go-git/v5](https://github.com/go-git/go-git) from 5.11.0 to 5.12.0.
- [Release notes](https://github.com/go-git/go-git/releases)
- [Commits](https://github.com/go-git/go-git/compare/v5.11.0...v5.12.0)
---
updated-dependencies:
- dependency-name: github.com/go-git/go-git/v5
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| |
| |
| | |
go-git/dependabot/go_modules/github.com/gliderlabs/ssh-0.3.7
build: bump github.com/gliderlabs/ssh from 0.3.6 to 0.3.7
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [github.com/gliderlabs/ssh](https://github.com/gliderlabs/ssh) from 0.3.6 to 0.3.7.
- [Release notes](https://github.com/gliderlabs/ssh/releases)
- [Commits](https://github.com/gliderlabs/ssh/compare/v0.3.6...v0.3.7)
---
updated-dependencies:
- dependency-name: github.com/gliderlabs/ssh
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| | |
Replace short field names with more descriptive ones.
|
| |
| |
| |
| |
| | |
The decision to change the name of these fields came from reading the code
further down in the scope and not being clear what `c.c` means.
|
|\ \
| | |
| | |
| | |
| | | |
go-git/dependabot/go_modules/github.com/skeema/knownhosts-1.2.2
build: bump github.com/skeema/knownhosts from 1.2.1 to 1.2.2
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [github.com/skeema/knownhosts](https://github.com/skeema/knownhosts) from 1.2.1 to 1.2.2.
- [Commits](https://github.com/skeema/knownhosts/compare/v1.2.1...v1.2.2)
---
updated-dependencies:
- dependency-name: github.com/skeema/knownhosts
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \
| | |
| | | |
git: Add commit validation for Reset
|
| | |
| | |
| | |
| | | |
Signed-off-by: Paulo Gomes <paulo.gomes@suse.com>
|
|\ \ \
| | | |
| | | | |
chore: fix some comments
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: avoidalone <wuguangdong@outlook.com>
|
|\ \ \ \
| | | | |
| | | | | |
git: Implement Merge function with initial `FastForwardMerge` support
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Introduces the Merge function for merging branches in the codebase.
Currently, the function only supports FastForwardMerge strategy, meaning it
can efficiently update the target branch pointer if the source branch history
is a linear descendant.
Support for additional merge strategies (e.g., three-way merge) will be added
in future commits.
Signed-off-by: Paulo Gomes <paulo.gomes@suse.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add a Merge function that behaves like git merge. This is a first
iteration that only supports --ff-only, which is the simplest type of
merge.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
plumbing: no panic in printStats function. Fixes #177
|
| | | | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
plumbing: object, Optimize logging with file.
|
| | | | | |
|
| | |/ /
| |/| | |
|
|\ \ \ \
| |/ / /
|/| | | |
git: worktree_commit, Fix amend commit to apply changes. Fixes #1024
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
plumbing: object, check legitimacy in (*Tree).Encode
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
git: worktree, Don't panic on empty or root path when checking if it is valid
|
|/ / /
| | |
| | |
| | | |
I didn't dig into the specific case that was triggering this, but we did have a panic in our production system.
|
|\ \ \
| | | |
| | | | |
plumbing: object, Make first commit visible on logs filtered with filename. Fixes #191
|
| | | |
| | | |
| | | |
| | | | |
Fixes #191
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
go-git/dependabot/go_modules/golang.org/x/net-0.22.0
build: bump golang.org/x/net from 0.21.0 to 0.22.0
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.21.0 to 0.22.0.
- [Commits](https://github.com/golang/net/compare/v0.21.0...v0.22.0)
---
updated-dependencies:
- dependency-name: golang.org/x/net
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
go-git/dependabot/go_modules/github.com/stretchr/testify-1.9.0
build: bump github.com/stretchr/testify from 1.8.4 to 1.9.0
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.8.4 to 1.9.0.
- [Release notes](https://github.com/stretchr/testify/releases)
- [Commits](https://github.com/stretchr/testify/compare/v1.8.4...v1.9.0)
---
updated-dependencies:
- dependency-name: github.com/stretchr/testify
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
go-git/dependabot/go_modules/golang.org/x/crypto-0.20.0
build: bump golang.org/x/crypto from 0.19.0 to 0.20.0
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.19.0 to 0.20.0.
- [Commits](https://github.com/golang/crypto/compare/v0.19.0...v0.20.0)
---
updated-dependencies:
- dependency-name: golang.org/x/crypto
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \ \
| | | |
| | | | |
remote: fetch, adds the prune option.
|
|/ / /
| | |
| | |
| | | |
Co-authored-by: Ludovic Fernandez <ldez@users.noreply.github.com>
|
|\ \ \
| | | |
| | | | |
Signer: fix usage of crypto.Signer interface
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
crypto.Signer was incorrectly used before. Signer documentation says
that Signer.Sign should be used on digests, whereas we were using this
on message bodies.
To fix this, create our own Signer interface (+ signableObject borrowed
from #705) that describes more accurately what we want.
As before, the expectation is that signer implementations only need to
worry about acting on encoded message bodies rather than needing to
encode objects themselves.
This is technically a breaking change from the previous Signer
implementation, but since this is new and hasn't made it into cut
release yet, this seems like an acceptible change.
Also adds example test showing how signers can be made (uses base64 for
consistent outputs).
|
|\ \ \ \
| |/ / /
|/| | | |
checkout-branch example
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
completes
|