Limited rollout of automatic DOIs

As a prelude to the general rollout of Dockstore’s new “automatic DOI” feature, we’ve enabled automatic DOI generation for published entries (workflows, notebooks, and .dockstore.yml-based tools) from the following GitHub organizations:

github.com/human-pangenomics/
github.com/NIH-CARD/
github.com/BD2KGenomics/
github.com/UCSantaCruzComputationalGenomicsLab/
github.com/dockstore/
github.com/dockstore-testing/
github.com/ucsc-cgp/
github.com/braingeneers/
github.com/DataBiosphere/

When a GitHub tag is pushed for one of those entries, Dockstore will automatically create a Zenodo “version” DOI corresponding to the tag, and create or update the Zenodo “concept” DOI corresponding to the entry:

https://docs.dockstore.org/en/stable/end-user-topics/dois.html#automatic-dockstore-doi-generation

During this “beta” period, as those organizations publish more entries, we’ll enable automatic DOI generation for them - however, it may be several days between when an entry is published and when we enable automatic DOI generation for it.

Automatic DOIs appear in the Dockstore Zenodo community:

https://zenodo.org/communities/dockstore

After we’ve confirmed the robustness of our new automatic DOI generation feature, we’ll enable it Dockstore-wide.

Should we refrain from pushing “too many” commits to branches in repos in these prefixes? Or is it fine to have dozens or hundreds of “version” DOIs on a concept?