Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.5.3 2024-02-14T08:47:27+00:00 2024-02-14T08:47:27+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-14T08:41:02+00:00 urn:sha1:c0847f928c32adb0b4dfc3b73ee77fa3cdb5ec21 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 2024-02-13T16:25:19+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-13T16:25:19+00:00 urn:sha1:1022344a0529b5f6b50f35d3030a528a1a5c6f91 this enables consistancy of display with simple clients that are just taking the output of `git format-patch` 2024-02-13T15:55:54+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-13T14:52:24+00:00 urn:sha1:cf319efc6dcdc6c54564cb84e13218edbf3643fa 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. 2024-02-13T06:27:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-13T06:27:34+00:00 urn: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 2024-02-09T07:21:00+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-09T07:21:00+00:00 urn:sha1:9cd3e43b899b23b7f6e75276fa3d19bf9550f8fd 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 2024-02-09T06:51:39+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-08T15:57:05+00:00 urn:sha1:4b0a35583644e703eb615e0724d33fe93aec932b format patch as a series in the patch event content unless it is 1/1 and there is no pr (cover letter) event 2024-02-02T06:51:40+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-02T06:44:28+00:00 urn: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 2024-01-26T21:32:21+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-01-26T21:32:21+00:00 urn:sha1:fc3f22eac2bb81823f170f61ba9d39baff76b933 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. 2024-01-26T19:47:03+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-01-26T19:47:03+00:00 urn:sha1:f212788263e39a6473c3a109a5eaf5b0bf8cd034 use fallback relays instead of more fallback relays 2024-01-23T00:00:00+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-01-23T00:00:00+00:00 urn:sha1:7e1f3a03ea4dea7b6aec39a555ce3caf22b88d8b this shouldn't be present