From 10498b953d36304b441fcb162155c2487046206f Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Mon, 22 Apr 2024 07:26:15 +0100 Subject: feat(send): `in-reply-to` tags npubs and events 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 --- src/sub_commands/push.rs | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src/sub_commands/push.rs') diff --git a/src/sub_commands/push.rs b/src/sub_commands/push.rs index bb50ee2..fefe102 100644 --- a/src/sub_commands/push.rs +++ b/src/sub_commands/push.rs @@ -108,7 +108,7 @@ pub async fn launch(cli_args: &Cli, args: &SubCommandArgs) -> Result<()> { cli_args, &sub_commands::send::SubCommandArgs { since_or_range: String::new(), - in_reply_to: Some(proposal_root_event.id.to_string()), + in_reply_to: vec![proposal_root_event.id.to_string()], title: None, description: None, no_cover_letter: args.no_cover_letter, @@ -166,6 +166,7 @@ pub async fn launch(cli_args: &Cli, args: &SubCommandArgs) -> Result<()> { None, None, &None, + &[], ) .context("cannot make patch event from commit")?, ); -- cgit v1.2.3