npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/test_utils/src/lib.rs, branch v1.1.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/atom?h=v1.1.02024-03-08T14:39:21+00:00feat(send): select commits from a list2024-03-08T14:39:21+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-08T14:37:56+00:00urn:sha1:6b3aecbcbde669859533716225e9c3bbfd2023b2
when since_or_range isn't specified
adds resilience as assuming master..HEAD can cause some issues
eg when master is not up-to-date with origin/master
refactor: improve rexpect error message2024-03-04T12:19:14+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-04T12:19:14+00:00urn:sha1:050d9978193d6e0802d045c2b6897117a5a90b61
to enable better debugging
test: ensure failed tests timeout2024-03-04T10:54:38+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-04T10:54:38+00:00urn:sha1:b02b4754c027bd751825c8e3b96766a5898187b1
resolve a long standing test issue where failures to output the correct
message in the cli would result in the test never ending
rather than failing
the many test cases updated in this change are to ensure
failures are caught rather than ignored
some of them are just refactored to remove calling an extra function,
which is no longer needed
note: this doesn't fix the intermittent issue, most commonly experienced
under the nix configuration, where tests that should pass
occationally never end preventing the rest of the suite from running
build: added to gitignore2024-02-29T13:09:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-29T13:09:47+00:00urn:sha1:df239f3536b08d295017f94d0a93c1c00a5039bc
so temporarly created test directories and files are ignored
feat(list): set checkout branch as default choice2024-02-20T16:48:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-20T16:22:10+00:00urn:sha1:141ebf0cc0c6cfea640debc9b9073303509a8bc7
instead of no default. note: I spent hours trying to get
CliTester to support default choices and gave up.
I have a stashed the attempt and am moving on...
feat!: nip34 set pr kind to patch kind2024-02-13T16:25:19+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-13T16:25:19+00:00urn:sha1:1022344a0529b5f6b50f35d3030a528a1a5c6f91
this enables consistancy of display with simple clients that are just taking
the output of `git format-patch`
test: fix backtrace display2024-02-13T15:55:58+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-13T15:34:21+00:00urn:sha1:2d6800b3aacc3b8ea223fc92ae7db1e2ae868109
between 5 Feb 2024 and 13 Feb 2024 backtrace began activiating in
`nix-shell` and ci during integration tests when rexpect.
this caused some error tests to fail / hang
it was not activating in the `nix-shell` when the cli
was called seperately
setting the `RUST_BACKTRACE=0` in the rexpect config surpresses
the backtrace as desired
feat(prs-create)!: pr to nip34-like cover letter2024-02-13T06:27:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-13T06:27:34+00:00urn:sha1:3112576195aef212622d27ad9164336796c1953e
up the pr event type to a nip34-like cover letter format
this sets the building blocks in place to enable simplier clients to
use the 'cover letter' feature in `git format-patch` to create the
experience as a pr event
feat(prs-create)!: use nip34 patch kind and tags2024-02-02T06:51:40+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-02T06:44:28+00:00urn:sha1:ccdbc337ae16d7c70be44166269c8b2d5b9f5c09
- change kind number
- remove "r-" prefix from unique commit id r tag
- rename tag commit-sig to commit-pgp-sig
- a tag for repo identifer and pubkey. this serves as a vote for
this pubkey being a maintainer
- add relay hints
- change format of committer tag
- remove r references to parent commit id
- tag parent patch event if its part of change request
author and commit-message tags still need to be removed but they are
required to apply patches with gitlib2. we will need to fallback to
running the git client to apply patches.
BREAKING CHANGE: change patch/commit event kind and tags to reflect
nip34 draft. events with the older kind will no longer be found and
will not be in a valid format
feat(repo_ref)!: align maintainers tag to nip34 style2024-02-02T03:11:31+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-02T03:11:31+00:00urn:sha1:401e60b98d94bc1f51dbd4b6083e92642a36efda
nip34 specifies that repo event tags with multiple values wuch as
"relays" and "web" use theformat:
`["tag", "item", "item"...]`
instead of:
```
["tag", "item"],
["tag", "item"],
```
this update also adds clarity. it is not obvious that using a p tag
is intended to make the pubkey a co-maintainer.
BREAKING CHANGE: format of maintainers tags in repo events has
changed to reflect nip34 style and ngit will not detect the old
format