npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/git_remote_helper.rs, branch v2.2.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.2.02024-09-09T08:40:19+00:00test: refactor into binary subdirs2024-09-09T08:40:19+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-09T08:40:06+00:00urn:sha1:9a9b13a11868fe58fa0390938a39483bf1f3cc9a
in prep for splitting git_remote_nostr tests
fix(remote): `fetch` and `list` status copy2024-09-06T13:06:03+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-06T12:07:29+00:00urn:sha1:ad28bd8db1a6e953dce999eea85becda1d90beae
so that it the filesystem url is shown
chore: bump rust-nostr to v0.34.02024-08-28T15:42:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-28T13:20:34+00:00urn:sha1:a5216602749bff55c2773acce098c91942cd3920
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
feat: set proposal branch prefix to `pr/`2024-08-20T05:25:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T05:25:17+00:00urn:sha1:fedf5166f0c57db14b9e43747121e4b7845b63dd
from `prs/`.
whilst plural reflects usage of `heads` and `tags` in git refs,
singular is shorter and more reflective of usage of branch prefixes
such as `feature/` `fix/`
feat(remote): `push` log merge event creation2024-08-18T07:14:29+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-18T07:14:29+00:00urn:sha1:de89a7ec528fa57702199f94e63b42f827bd2fdf
so the user knows that a merge commit event will be issued
feat(remote): `push` publish merge event2024-08-18T07:04:49+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-18T07:04:49+00:00urn:sha1:948c8595acea9a783a38002371c40185868ce923
when a merge commit is being pushed that merges a patch in a proposal
feat(remote): `push` new proposal2024-08-09T07:40:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-09T07:35:53+00:00urn:sha1:5618fd9883d45de1443a40abada944cbe3bb8dfd
issue new proposal when new branch is pushed into `prs/*` namespace,
which doesn't match an existing proposal
feat(remote): remove pr id postfix for authors2024-08-09T07:25:43+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-09T07:25:43+00:00urn:sha1:d1f1963a34ec66356e1b66c1fce937391dd126c3
remove the (<short id>) post fix for remote proposal branches when
the current user is the author
this enables pushing new proposals without having to change the
upstream branch in a way that remote helpers weren't designed to do
fix(send): patch count2024-08-08T16:53:42+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T16:53:42+00:00urn:sha1:a556464452789dc72cb9b0bff8e9ba6addc6639a
fix [PATCH n/n] when no cover letter and patches great than 1
fixes error where the first patch would be
[PATCH] followed by [PATCH n/n]
feat(remote): `push` force push proposal2024-08-08T16:36:44+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T16:34:40+00:00urn:sha1:9971f23a184d57600ea9b1962910d32bf6aec185
will issue a proposal revision