| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: avoidalone <wuguangdong@outlook.com>
|
|\
| |
| | |
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
|
| |
| |
| |
| | |
Co-authored-by: Johannes Huning <johannes.huning@gmail.com>
|
|/ |
|
|\
| |
| |
| |
| | |
go-git/dependabot/go_modules/golang.org/x/net-0.21.0
build: bump golang.org/x/net from 0.20.0 to 0.21.0
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.20.0 to 0.21.0.
- [Commits](https://github.com/golang/net/compare/v0.20.0...v0.21.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>
|
|\
| |
| | |
plumbing: format/gitattributes, close file in ReadAttributesFile
|
| |
| |
| |
| | |
Fixes #1017
|
|\ \
| |/
|/| |
_example: fix 404 link and added ssh-agent clone link
|
|/ |
|
|\
| |
| | |
build: Bump github.com/sergi/go-diff
|
| |
| |
| |
| | |
Signed-off-by: Paulo Gomes <paulo.gomes@suse.com>
|
|\ \
| | |
| | | |
Worktree.AddWithOptions: add skipStatus option when providing a specific path
|
| |/ |
|
|\ \
| | |
| | | |
Add crypto.Signer option to CommitOptions.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change adds a new crypto.Signer option to CommitOptions as an
alternative to SignKey to allow alternative commit signers to be used.
This change byitself does not add other signing methods (e.g. ssh,
x509, gitsign), but gives callers the ability to add their own.
This roughly follows git's sign_buffer approach where go-git handles the
commit message body encoding, and hands off the encoded []byte to the signing
implementation for the signature to be returned.
Signed-off-by: Billy Lynch <billy@chainguard.dev>
|
|\ \
| | |
| | |
| | |
| | | |
go-git/dependabot/go_modules/github.com/ProtonMail/go-crypto-1.0.0
build: bump github.com/ProtonMail/go-crypto from 0.0.0-20230828082145-3c4c8a2d2371 to 1.0.0
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [github.com/ProtonMail/go-crypto](https://github.com/ProtonMail/go-crypto) from 0.0.0-20230828082145-3c4c8a2d2371 to 1.0.0.
- [Release notes](https://github.com/ProtonMail/go-crypto/releases)
- [Commits](https://github.com/ProtonMail/go-crypto/commits/v1.0.0)
---
updated-dependencies:
- dependency-name: github.com/ProtonMail/go-crypto
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \
| | |
| | | |
object: fix variable defaultUtf8CommitMessageEncoding name spell error
|
| |/ |
|
|\ \
| |/
|/| |
Add example for git clone using ssh-agent
|
|/
|
|
| |
Signed-off-by: Paulo Gomes <paulo.gomes@suse.com>
|
|\
| |
| | |
utils: update comment in node.go's Hash()
|
|/
|
|
| |
This reflects the lazy hash calculation and the implications of this.
|
|\
| |
| | |
Calculate filesystem node's hash lazily.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The main motivation behind this change is to speed up status operation.
Currently it's very slow, especially for repositories with lots of ignored
files (e.g. node.js repository with node_modules directory).
One of the reasons for this slowness is the fact that traversing filesystem
involves calculating file hashes for all files, even if those hashes are
not needed in the end because the files are in gitignore.
On my machine, for a random repository with sizable (ignored) node_modules
directory this changes bring the execution time for Worktree.Status
from ~3.5s to ~1.4s. This is still very slow, but a significant improvement.
A better fix (instead of or in addition to this one) would be to avoid traversing
ignored files in the first place. However, such change seem to be more
intrusive and will require much deeper understanding of the codebase.
|