upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/src/sub_commands/send.rs
AgeCommit message (Collapse)Author
2024-02-29feat(send): add proposal revision cli msgDanConwayDev
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
2024-02-28fix: branch-name specified as main or masterDanConwayDev
branch-name should be ommitted or ignored if patches created on main or master instead it should be infered based on commit msg
2024-02-23feat(init): add customisation and defaultsDanConwayDev
- 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
2024-02-23fix(push): remove force push bugDanConwayDev
introduced in b931b37e26486e4e6d15f302e87141dcf2f596ba
2024-02-23refactor: remove confusing options, improve helpDanConwayDev
from_branch and to_branch have been replaced by specifying revision ranges
2024-02-23refactor: remove confusing options, improve helpDanConwayDev
from_branch and to_branch have been replaced by specifying revision ranges
2024-02-23feat(push): add `--force` to issue revisionDanConwayDev
wrapping `send --in-reply-to` unless branch up-to-date
2024-02-22fix(list): support `--in-reply-to` latest revisionDanConwayDev
update list to support rebases via proposal revisions as created by `ngit send --in-reply-to` or upcoming change `ngit push --force`
2024-02-21feat(send): in-reply-to arg for revised proposalDanConwayDev
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
2024-02-21feat(send): specify commits eg HEAD~2DanConwayDev
specifiy commits or commit ranges in the same way that `git format-patch` allows
2024-02-20feat(list): download or apply with git amDanConwayDev
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
2024-02-20refactor: simplify commit msg extractionDanConwayDev
and create functions to use this for non-root patches
2024-02-20fix: cover letter description from patchDanConwayDev
if description isn't present this was causing an breaking error
2024-02-19fix: ingore patch diff in descrition fallbackDanConwayDev
the description is not currently displayed so no tests where written
2024-02-16refactor: added code commentsDanConwayDev
to reflect the requirement for certain tags
2024-02-16refactor: rename PR to proposalDanConwayDev
PR is a problematic term when it ambiguous whether the set of patches are PR-like or email-patch like.
2024-02-14feat: send to default relays, blast repo eventDanConwayDev
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
2024-02-14feat!: move `prs create`>`send`, `prs list`>`list`DanConwayDev
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