This appears to be an error, so I'm closing. This proposal arrived as an issue and was then buried.
nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr
Discussion
Is there an outstanding problem with ngit gitworkshop.dev you are trying to highlight here? I thought ngit v1.3-beta1 fixed the issue you previously raised.
This is something different. I have no idea how nostr:npub1nf9vm6uhs4j7yaysmjn9eqlf7et5t6hvrkdqgpd995vcc9yfjyas0pxa3x proposal ended up in the issue.
He then added a proposal that loaded correctly, so I initially didn't see this note.
I am still new-ish to git, so maybe I did something out of order.
that shouldn't be possible
Can you explain what the problem is?
I can see:
1) the proposal with a merged status. The is the rootiof this discussion thread.
2) the following issue that references the proposal: nostr:nevent1qqstsczw4lxjdtwnysemzg8sjl3ythhf7va2h63lrwt4lkdu8m9kvcgppemhxue69uhkummn9ekx7mp0qgsd6ejdteqpvse63ntf7qz6u9yqspp4z7ymt8094urzwm0x2ceaxxgrqsqqqpj4lmcdjx
These are displaying as expected for me on gitworkshop.dev
I guess I'm confused by this. I only see one proposal in my repo.
What am I looking at, here.
I thought I had one issue and one proposal from James, but here are two proposals.
I'm confused.
I see whst you mean now. I wasn't looking at the recent proposals section on the homepage.
What you are seeing is one cover letter and one commit from the same proposal but listed separately.
There are two problems uncovered here:
1) 'recent proposals' should just show the proposal root and not each each commit.
2) links to a commit (or a reply for that matter) should take you to the proposal page with the specific commit / reply highlighted.
I'll look onto this next week.
Ah, I see! I was like Wut?
Thanks for reporting and clarifying.