DanConwayDev on Nostr: It's good but not essential for each maintainer to issue a repo event. In this case ...
It's good but not essential for each maintainer to issue a repo event. In this case it appears two npubs have issued an announcement listing different, but overlapping maintainers.
When you select a repo annoucement, it will display all the proposals and issues that tag that announcement or the corresponding announcements of the other maintainers it lists. Irrespective of whether or not they have issued one yet.
Similarly, if you create an issue it will tag it with the same set of announcement events.
Does this make any sense?
Ngit sort of works like this as well.
There is certainly a lot of room for improvement on how related and unrelated announcements that share an identifier get listed on the https://gitworkshop.dev/repo page. Suggestions welcome.
Do you think the author of the announcement needs to be more prominent somehow when there are additional maintainers?
When you select a repo annoucement, it will display all the proposals and issues that tag that announcement or the corresponding announcements of the other maintainers it lists. Irrespective of whether or not they have issued one yet.
Similarly, if you create an issue it will tag it with the same set of announcement events.
Does this make any sense?
Ngit sort of works like this as well.
There is certainly a lot of room for improvement on how related and unrelated announcements that share an identifier get listed on the https://gitworkshop.dev/repo page. Suggestions welcome.
Do you think the author of the announcement needs to be more prominent somehow when there are additional maintainers?