| Age | Commit message (Collapse) | Author |
|---|
|
refactor to address breaking changes in rust-nostr
fix a number of in dependancy which have been upstreamed
|
|
using the same dependancies in ci as in development
|
|
rust-nostr author suggested this might be a false positive
https://github.com/rust-nostr/nostr/pull/375#issuecomment-2022245832
|
|
caused by test proposals with the same timestamp
listed in an inconsistant list order;
by ensuring test proposals have a different timestamps
|
|
yukibtc released a patch to address intermittent problem
fetching events, which caused our integration tests to fail
|
|
as patch accepted into package
|
|
to address send_event_to spurious timeout error
|
|
upgrade from rust-nostr v0.27 ~> v0.28 introduces this panic
presumably get_events attempted to write to the MultiProgress
just after it has been removed
|
|
to suppress the clippy too_many_lines in function warning
|
|
as it has been removed from nostr_sdk
|
|
to reflect changes in rust-nostr
|
|
to reflect new name in rust-nostr
|
|
to reflect new name in rust-nostr
|
|
it had moved from 'prelude' to 'hashes'
|
|
to reflect new name in rust-nostr
|
|
both nostr and nostr-sdk packages and also in test_utils
|
|
update nix dependancies to latest version using default update options
|
|
update dependancies to latest version stated in cargo.toml
|
|
changelog:
* fix stack overflow bug when origin remote doesnt exist
|
|
introduced in 098b0258fdd581c750099cb463adbddb57843388
|
|
changelog:
* `ngit send` - improve proposal commit
|
|
catch more errors when proposed commits
are not connected to origin/main branch
improve default selected commits when on main branch
|
|
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
|
|
which is covered by a test case.
broken by:
445eea13d987b345535fd4fa56486ff334bbd351
|
|
to enable better debugging
|
|
fixing error which should have been resolved in:
8519dc4a10d47747e6df3f47e25c36bf16befe00
|
|
instead of the latest commit. issue intrroduced in:
445eea13d987b345535fd4fa56486ff334bbd351
|
|
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
|
|
change donwload ~> download
|
|
pointing to gitworkshop.dev for more details
|
|
refer to a single patch as patch rather than patches
|
|
based on feedback from santos:
nostr:31c085a584cbd30f71a44a70eaf828c2c8c5f6e3efb7942547edb37cf4a632cf
|
|
following semantic versioning, this release includes breaking changes
so it has a new major version
this is not reflection on its stability
|
|
so temporarly created test directories and files are ignored
|
|
before cover letter prompt
primarily this is to make it clearer that a proposal update
is being sent when using `ngit push --force` instead of
a new proposal
|
|
as runs are now taking slightly longer than 5 minutes
|
|
branch-name should be ommitted or ignored if
patches created on main or master
instead it should be infered based on commit msg
|
|
with introduction, commands and how to contribute
|
|
show proposals in order newest first
|
|
move instruction to commit and push maintainers.yaml to end of file
|
|
- allow more cli input options
- allow customisation of more fields in interface
- change default identifer from shorthand root commit to short name
- defaults to existing repo event (users or other) or maintainers.yaml
|
|
introduced in b931b37e26486e4e6d15f302e87141dcf2f596ba
|
|
from_branch and to_branch have been replaced
by specifying revision ranges
|
|
from_branch and to_branch have been replaced
by specifying revision ranges
|
|
wrapping `send --in-reply-to` unless branch up-to-date
|
|
introduced in
9f1d8cd964a04197565a2acb1f2b174c9582d333
|
|
ammended should read amended
|
|
added test to cover local propsal being amended
this should catch error for rebased proposals as well
|
|
reduce wording in choices
|
|
previously these commits would be skipped
|
|
also updated copy and code comments
|
|
to align with changes done to pull
c5dfd1b7e509eedc33de75343de8659e3c9e0b2a
also improved copy
|
|
to align with changes done to pull
c5dfd1b7e509eedc33de75343de8659e3c9e0b2a
also improved copy
|
|
also updated copy and code comments
|
|
add test for scenario
|
|
add test for scenario and tweak copy
|
|
added tests to cover one of these rebase scenarios
|
|
and added some comments to better describe the rebase scenarios
|
|
update list to support rebases via proposal revisions
as created by `ngit send --in-reply-to`
or upcoming change `ngit push --force`
|
|
send a revised version of a proposal using the new in-replyto argument
suppliments existing 'root' tag with 'root-revision'
e 'reply' tag to the original proposal
|
|
specifiy commits or commit ranges in the
same way that `git format-patch` allows
|
|
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...
|
|
if a revision responds to a root patch (no cover letter)
then the revision will nolonger be applied on top of
the first patch in the original set
|
|
remove the word nostr for consistency and as its a bit confusing
|
|
add the option to download patches or apply them with git am
give more granular messages about the state of proposals.
add support for replacing old proposal version with a new one
|
|
and create functions to use this for non-root patches
|
|
if description isn't present this was causing an breaking error
|
|
when trying to create a branch from a proposal
when the the parent commit id doesnt exist
|
|
the description is not currently displayed so no tests where written
|
|
broken in 701668b02d999af42f51d8bd25fffb2a8692c3c8
|
|
to reflect the requirement for certain tags
|
|
PR is a problematic term when it ambiguous whether the
set of patches are PR-like or email-patch like.
|
|
instead of commit ids as part of nip34 compliance and to enable
applying proposals to tip of master in the future
|
|
minor improvement to error message
|
|
as part of nip34 compliance
|
|
improve summary for help commands
|
|
because they take 3 minutes to run and sometime fail due to
a nix specific issue
|
|
instead of no default
|
|
nostr configuration file to make it easy ngit users to find events
|
|
previously filtering for d tag rather than a tag
this kind of bug should be picked up by tests when our
mock relay is applying filters before sending events
|
|
previously looking for p tag rather than author
this kind of bug should be picked up by tests when our
mock relay is applying filters before sending events
|
|
it wasn't clear why no results were coming back from relays
or why it is needs (added reference to relay updates)
|
|
also add a default web
|
|
wss://eden.nostr.land is a paid relay
wss://nostr.wine is paid relay
|
|
0b9c7521b035e60ad7c458c1e782623e18a5cc21 set this to 20 minutes from 6h
but it only 3m to run on each channel
|
|
add a ui feature to countdown to timeout so user doesn't consider
exiting early
|
|
if repo event cannot be found using unique commit the user can
find it via a nevent or naddr
also handle no PRs found
|
|
improve the distribution of events by sending to default relays
in addition to user and repo relays. for better discoverability of
repo events, this is also blasted.
a temporary fix to blast everything was removed.
the less reliable purplepages.es relay is moved to
more_fallback_relays that currently isn't used
|
|
Improve how progress is reported in the UI when fetching events
|
|
this aligns with gitstr and is more intuative
the idea behind using claim to indicate that it is only for
maintainersto do is valid but its too confusing
|
|
remove unnecessary hierachy of `prs` which is also a troublesome term
replace the concept of `create` which aligns more to the PR github model
to `send` which aligns more with the git patch model
|
|
this enables consistancy of display with simple clients that are just taking
the output of `git format-patch`
|
|
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
|
|
use first patch as thread root if pr event isn't present.
begin renaming pr event to cover letter.
fix patch ordering upon creation. patches were in youngest first
order which caused:
- `PATCH n/t`to be in reverse order
- the youngest patch was the marked root
- oldest patch replied to the youngest
fix finding most recent patch event. when a patch in a set is the
most recent it will share a created_at with other patches.
previously the first patch recieved from relay in the set would be
used. now it finds the first patch with that created_at which isn't
also a parent of another patch with the same created_at.
|
|
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
|
|
this is simpler
there is no need to check whether main or master exist
because one does 99+% of the time
the root commit wil be te same for head as master 99+% of the time
|
|
format patch as a series in the patch event content unless it is 1/1
and there is no pr (cover letter) event
|
|
this overrides the default timeout of 6h which is excessive
|
|
This is intended to improve the reliabilty of the tests. there have been
particular issues with random tests never ending when run in the nix
configuration
see discussion here
https://github.com/DanConwayDev/ngit-cli/issues/
6#issuecomment-1918971239
and:
https://github.com/DanConwayDev/ngit-cli/pull/7
|
|
- 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
|