| Age | Commit message (Collapse) | Author |
|---|
|
as a simple proxy to the first git server listed in announcement
parse clone url as `nostr://naddr123...`
|
|
add missing or updated identifier to maintainers.yaml
as we were not checking whether it has changed or added
also update if relays do not match
|
|
instead of Kind::Custom(u16) as v33 of rust-nostr introduced them
|
|
if branch is ahead of main or master
|
|
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
|
|
when finding repo announcements
add a hint to find naddr on gitworkshop.dev
|
|
bump all rust-nostr packages
move from using patched nip46 nip05 function to profile function in v33
fix send_events_to error message
|
|
when looking for proposal roots 'pull' was not filtering out
proposal revisions
issue identified in failing test, which it now passes
|
|
as part of a project to use fetch and the stored cache everywhere
|
|
as soon as they are successfully sent to at least one relay
|
|
as part of a project to use fetch and the stored cache everywhere
|
|
the last set of pull integration test fails:
when_latest_event_rebases_branch
we are planning on replacing pull so I'm not sure
whether it is worth fixing
|
|
as part of a project to use `fetch` and the stored cache everywhere
|
|
to proposal which is displayed at the end of the functon
|
|
reworking the tests and test suite as appropriate
|
|
when fetching a user profile from user relays it throw an error
when an existing version of the profile wasn't found
|
|
prevent an infinite loop when a new maintainer is identified
that hasn't issued a repo event yet
make it clear when repo_coordinates must not have relays
|
|
as any profile event was being recorded as a update
|
|
rather than ending the loop without fetching them
|
|
prevent infinite loop when new coordinates are found
|
|
into cache directory rather than config directories
also removed CodeCollaboration from path as this isn't helpful
whilst this is a breaking change, the cache was only introduced
during development of this version so it is not
highlighted as such
|
|
rather than as new profiles
|
|
add a message for the temporary situation where a maintainers.yaml
exists without an identifier listed
|
|
add the ability to fetch more than just the current user from
their user write relays
|
|
which will enable the following`list` test to pass once `fetch`
is intergrated into `list`:
finds_based_on_naddr_on_embeded_relay
|
|
only the profile from the saved user was being fetched.
tests are using cli login parameters and expecting to see the
user's name but it was only showing the npub.
fixed by allowing the explicit request of specfic user profiles.
|
|
set repo.nostr to naddr reflecting the announcement just issued
|
|
fetch automatically gets updates to logged in user profile / relays
fetching without specifying repo pointers will just fetch user
profiles so that can be used during login, if user profile isn't
in cache
login now uses fetch
|
|
just from repository / fallback relays and only if we don't already
have a version in cache
this is because we are only using it for the user's name
|
|
as 'fetching... updates:' feels more like further updates are
being fetched than 'fetching... found'
|
|
so it only counts commits and statues to existing proposals
|
|
to increase the likelihood that all events are found
|
|
im preparation for identifying new inbox relays
|
|
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'
|
|
a typo prevented fetching of saved bunker-uri and therefore ngit
would act as if it wasn't saved
|
|
disable event limits in rust-nostr which cause large patches to be filtered out
|
|
if the maintainers tag is omitted
|
|
instead of just tagging the first maintainer's repo event and each
maintainer with a p tag
This allows for easier discoverability of the proposal when:
* the first maintainer hasn't issued a repo event
* the maintainers change over time and the single tagged repo event
is no listed as a maintainer in anyone elses repo event
|
|
currently using patched version of rust-nostr with function to fetch
nip46 relays from nip05 providers. this patch has been merged so it
will make it into the next rust-nostr release.
|
|
and save details in git config
|
|
so that nip46 bunker signing can be added
|
|
ensure fresh global cache when under test conditions by conditionally
storing it in local ./git folder
|
|
replace ngit yaml file config with:
* nsec / ncryptsec / npub in git config in nostr.* namespace
* sql database cache for metadata and relay events
allow different logins to be used for different git repositories by
storing login in local git config
|
|
local or global but tests only added for local
|
|
based on nip34 update.
see nip repository commit 8fe6e062254b37f77540088cccff60fa8615751
|
|
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
|
|
bump nostr and nostr-sdk packages and also in test_utils
remove custom ncryptsec implementation and use the newly
added implementation nip49 version in rust-nostr
note a patched v0.30 is used so that log_n is exposed so that
user can be warned it might take a few seconds to decrypt.
this has now been merged into the library.
note that this will no longer decrypt existing ncryptsec values as
it is uses a longer string. this should therefore be bundled with
the upcoming change to storing nsec and ncryptsec in git config.
|
|
to repo announcements, patches and cover letters
|
|
fixes:
nostr:nevent1qqsz2g7gexkmqgr0x4g5kf9py8vx06p8nyn78v7mhevprasnyfy5swcpp4mhxue69uhkummn9ekx7mqzyr7jprhgeregx7q2j4fgjmjgy0xfm34l63pqvwyf2acsd9q0mynuzdyll0c
|
|
in addition to being used to create a new proposal revision,
in-reply-to can now be used to reference other events and npubs.
for example an issues or kind 1 threads where the proposal is relevant
the proposal will only be marked as a revision if the first parameter is
a reference to an existing proposal root
|
|
as over the last 2-3 weeks it has consitantly be timing out
|
|
after a new root proposal has been sent
link directly to gitworkshop.dev as well as njump.me until
gitworkshop is added to njump
|
|
seperate connection timeout from get_events_of timeout and reduce it to 3s
|
|
in line with initial merged nip34 spec
|
|
if relays do not connect and retun events within 3s
they will rarely connect at all
this could be reversed when get_events is used async
|
|
rust-nostr author suggested this might be a false positive
https://github.com/rust-nostr/nostr/pull/375#issuecomment-2022245832
|
|
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
|
|
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
|
|
update nix dependancies to latest version using default update options
|
|
update dependancies to latest version stated in cargo.toml
|
|
introduced in 098b0258fdd581c750099cb463adbddb57843388
|
|
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
|
|
fixing error which should have been resolved in:
8519dc4a10d47747e6df3f47e25c36bf16befe00
|
|
instead of the latest commit. issue intrroduced in:
445eea13d987b345535fd4fa56486ff334bbd351
|
|
change donwload ~> download
|
|
refer to a single patch as patch rather than patches
|
|
based on feedback from santos:
nostr:31c085a584cbd30f71a44a70eaf828c2c8c5f6e3efb7942547edb37cf4a632cf
|
|
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
|
|
branch-name should be ommitted or ignored if
patches created on main or master
instead it should be infered based on commit msg
|
|
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
|
|
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 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
|