| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BuildTree now returns an ErrEmptyCommit error, when there are no
changes to be committed. This can be opted-out via
CommitOptions.AllowEmptyCommits.
This is a breaking change which enables applications to detect when
empty commits are to be created.
Some instances in which this can occur is when the fs (e.g. `billy/osfs`)
make changes to the underlying files, causing a conflict between what
the previous Git worktree state was, and the current state. Changes to
the fs implementations are orthogonal to this, and will be dealt with
separately.
The new behaviour aligns with the Git CLI, in which empty commits
returns the error message: 'nothing to commit, working tree clean'.
Signed-off-by: Paulo Gomes <pjbgf@linux.com>
|
| |/
|
|
|
|
| |
Adds an Amend option to CommitOptions that behaves like git --amend.
This change includes modifications to the Validate function to disallow
a Commit call with both Amend and either Parents or All enabled.
|
| |
|
|
|
|
|
|
| |
[staticcheck](https://staticcheck.io/) reported a number of unused
fields, functions, types, and variables across the code.
Where possible, use them (assert unchecked errors in tests, for example)
and otherwise remove them.
|
| | |
|
| |
|
|
| |
github.com/ProtonMail/go-crypto/openpgp (#283)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix cloning large repositories
Ignore the error on close when the connection is already closed
Fixes #70
* Compatibility for go 1.13
Because it's required by the pipeline
* Add test for allowing to close a command when the client is already closed
This test is for issue #70
* Add debug information for broken test
|
| |
|
| |
* git: worktree_commit, just store objects not already stored
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
When we assign a value to err, make sure to also check for it being nil
afterwards. If those were intentionally unchecked, we should remove the
assignment in the first place. Those checks certainly never harm, but please
review thoroughly and let me know.
Signed-off-by: Christian Muehlhaeuser <muesli@gmail.com>
(cherry picked from commit 19d6f42a4d814a50bd262fbb69a9b670db9756a2)
|
| |\ |
|
| | |
| |
| |
| | |
Signed-off-by: kuba-- <kuba@sourced.tech>
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Mark Bartel <github@spottybenny.ca>
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Mark Bartel <github@spottybenny.ca>
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The old one was created with defaults, which would have caused CI
failures in 2 years.
The new one is valid for 10 years:
> gpg --list-secret-keys
/root/.gnupg/pubring.kbx
------------------------
sec rsa4096 2018-08-22 [SC] [expires: 2028-08-19]
93A17FF01E54328546087C8E029395402EFCCD53
uid [ unknown] foo bar <foo@foo.foo>
Signed-off-by: Chris Marchesi <chrism@vancluevertech.com>
|
| | |
| |
| |
| |
| |
| | |
I'm hoping this helps get codecov to a tolerable delta. :)
Signed-off-by: Chris Marchesi <chrism@vancluevertech.com>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will not work for a signed commit as with the GPG signature being a
part of the commit, the hash is now non-deterministic.
Verification of the commit is done through the validation of the
signature.
Signed-off-by: Chris Marchesi <chrism@vancluevertech.com>
|
| | |
| |
| |
| |
| |
| |
| | |
This was added in Go 1.10 and is not supported on Go 1.9. Switched to
bytes.Buffer to ensure compatibility.
Signed-off-by: Chris Marchesi <chrism@vancluevertech.com>
|
| |/
|
|
|
|
|
|
|
|
| |
This adds the ability to sign commits by adding the SignKey field to
CommitOptions. If present, the commit will be signed during the
WorkTree.Commit call.
The supplied SignKey must already be decrypted by the caller.
Signed-off-by: Chris Marchesi <chrism@vancluevertech.com>
|
| |
|
|
| |
Signed-off-by: Máximo Cuadros <mcuadros@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
