| Age | Commit message (Collapse) | Author |
|---|
|
the make the code more readable
this commit just moves the files, the next commit should fix the imports
|
|
bump all rust-nostr packages
I'm not sure I'm completely happy with allowing mutable_key_type
but it is just run inside tests
it appears that Event didn't have the Copy trait in v0.33.0 so I'm
not sure why this warning suddenly appeared
the timeout of client.get_events_of needed to be doubled which could
indicate that an ineffiency has been introduced in v0.34.0
the primary motivation for upgrading now was to get this fix:
nostr:nevent1qqsffl2ld678pjj77rh9k2g4edljmxdu6ew4lvgnglxv7jhu3ru8vvcpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6rm2ucm
as I suspect it is also effecting other repositories
eg nostr-profile-manager
|
|
instead of Kind::Custom(u16) as v33 of rust-nostr introduced them
|
|
to prevent accidental name conflicts. also moved to prs/* namespace
`pull` and `push` integration tests are intermitantly failing to end
at least for `push` they work when run individually but not
when run together
|
|
as part of a project to use fetch and the stored cache everywhere
|
|
enabler to add simplicity, efficency and offline
capability to other functions
improve repo announcement selection
|
|
show open proposal by defult and include options to filter
by other statuses
there are not tests for this currently as the intention is
to transform 'list' further by adding a 'fetch'
|
|
both nostr and nostr-sdk packages and also in test_utils
fix the many breaking changes
fix: ignore trailing slash when depuplicate relays for send events.
this was picked up as TagStandard::RelayMetadata has started adding
a traling slash.
refactor cli output test function `expect_send_with_progress` so that
relays can succeed / fail in a random order
|
|
to reflect changes in rust-nostr
|
|
update nix dependancies to latest version using default update options
|
|
catch more errors when proposed commits
are not connected to origin/main branch
improve default selected commits when on main branch
|
|
show proposals in order newest first
|
|
- 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
|
|
ammended should read amended
|
|
reduce wording in choices
|
|
also updated copy and code comments
|
|
to align with changes done to pull
c5dfd1b7e509eedc33de75343de8659e3c9e0b2a
also improved copy
|
|
add test for scenario and tweak copy
|
|
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`
|
|
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
|
|
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
|
|
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
|
|
as part of nip34 compliance
|
|
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
|
|
if repo event cannot be found using unique commit the user can
find it via a nevent or naddr
also handle no PRs found
|
|
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
|