npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/sub_commands/claim.rs, branch v1.1.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.1.12024-02-14T08:54:27+00:00feat!: move `claim` > `init`2024-02-14T08:54:27+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-14T08:54:27+00:00urn:sha1:62d7f2fb26f2843fa8f7ff8b988bac14e5f756e2
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
feat!: move `prs create`>`send`, `prs list`>`list`2024-02-14T08:47:27+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-14T08:41:02+00:00urn: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
refactor(git): find root commit from head2024-02-09T07:21:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-09T07:21:00+00:00urn: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
feat(repo_ref)!: use nip34 kind and tags2024-02-02T02:30:01+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-01T09:59:09+00:00urn:sha1:1cacf1bce77b88febc0cf9e2f0f9f468d4b30555
- 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
feat(claim): add blaster to relay list2024-01-26T20:04:20+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-26T20:04:20+00:00urn:sha1:d5058d11caad038fca493c988ff173d30de07672
this is a temporary fix until we handle relays more effectively
feat(claim): improve no remote error message2024-01-22T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-22T00:00:00+00:00urn:sha1:9200b96bd8fe7ac254e41048790d7411937c3f95
so that the user knows why a remote is required
feat(claim) create yaml add maintainers and relays2023-12-12T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2023-12-12T00:00:00+00:00urn:sha1:3e52ecb609f8424cffb2e6398c599aa78224825a
- 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
refactor(claim) move repo_ref.rs2023-11-01T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2023-11-01T00:00:00+00:00urn:sha1:82f1ba360b60c8339c7caea0dec7903ee5e764cd
file created in the wrong folder in error
refactor(claim) remove setter flow2023-11-01T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2023-11-01T00:00:00+00:00urn:sha1:36de3b05e61130f0c279419edeac8bba534a3791
we dont need to th verbose of getters and setters for this right now
refactor(claim) add RepoRef struct2023-11-01T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2023-11-01T00:00:00+00:00urn:sha1:c37ceaf1c3e4371f320798bf423719a9a6fe71fd
enable wider usage of repoistory reference details