Right now it assumes the blossom state is always reflected in the latest 30618 event. This means it will only upload state for branches / tags that have had changes since blossom was added to the `clone` list.
Discussion
If there is no blossom sha256 for a tag, it cannot be cloned from blossom. I think it is not the expected behaviour from the user. If he makes the move from github to blossom, then removes github.com clone url from the repo announcement even, then he will be disappointed if he cannot clone old versions.
I think blossom keys should be added to each ref upon the first push to blossom to keep the functionality.
given nostr:nevent1qvzqqqqqqypzpn7hma38nx3zuwz2f26a4rzqymy8tvge6r68cfckkgxd4jwvrudxqyt8wumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6tcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgkwaehxw309ac82unsd3jhyetvv9ujucm0d5hszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqzqt866gp6x070sw7zyay538f4jp9k707x3dt29z5fdzpacwuzem0s4ryegr this could be easily solved by calculating state via the 30618 tags that have a sha256sum listed.