| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
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
|
|
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
|
|
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'
|
|
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
|
|
and save details in git config
|
|
so that nip46 bunker signing can be added
|
|
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
|
|
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 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
|
|
after a new root proposal has been sent
link directly to gitworkshop.dev as well as njump.me until
gitworkshop is added to njump
|
|
in line with initial merged nip34 spec
|
|
to suppress the clippy too_many_lines in function warning
|
|
to reflect changes in rust-nostr
|
|
to reflect new name in rust-nostr
|
|
it had moved from 'prelude' to 'hashes'
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
the description is not currently displayed so no tests where written
|
|
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
|
|
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
|
|
also add a default web
|
|
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
|
|
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`
|
|
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
|
|
- 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
|
|
- change kind number
- do not rely on d identifiers for unique commit id. set it as default
to unique commit id shorthand.
- remove "r-" prefix from unique commit id r tag and instead add checks
for SHA1 validity
- rename tag git_server to clone
- add web tag
- use single relays tag instead of multiple relay tags
BREAKING CHANGE: change repo 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
|
|
this is a contribution from jk (sectore) that I rebased and squashed
into this commit.
the tests were broken in the last few commits to rush out some fixes.
this change may introduce more issues because of
Relay.respond_standard_req.
|
|
instead of the `more_fallback_relays`
|
|
this is a temporary fix until we handle relays more effectively
|
|
use fallback relays instead of more fallback relays
|
|
this shouldn't be present
|
|
before applying changes and bail if not
|
|
before checking out PR branch
add confirm prompt before checking out branch and applying changes
|
|
so that commit ids can be maintained
|
|
so that the user knows why a remote is required
|
|
- create yaml file with maintainers and relays
- add maintainers to repo event
- add current user as maintainer
- custom repo relays from cli argument
- save git-server in repo event
|
|
- find pr with a branch-name that matches checked out branch
- check branch isnt behind latest patch on pr
- push new commits a patches associated with pr
|
|
- find pr event which matches branch name
- fetch and apply latest commits
|
|
- fetch prs and present as a selectable list
- create and / or checkout branch for selected pr
- apply latest patches as commits
|
|
tag pr event with title, description and the name of the current
checkedout branch
|
|
r tags are indexed by relays in they same way as t tags and are a more
appropriate for referencing commits
|
|
fetch repository reference events to identify repository relays
send pr events to repository relays alongside user relays
|
|
file created in the wrong folder in error
|
|
we dont need to th verbose of getters and setters for this right now
|