Detailed Zenodo instructions for new software DOI?

[pllim]

I see that there is a mention of Zenodo in software-versioning.md but no instructions on the recommended way to do it. For example: How to set up GitHub webhook, how to specify certain fields like #95, etc. Also, would the recommendation be a separate DOI for each release or a blanket DOI for the entire package.

I feel like there were discussions about these things and @brechmos-stsci came to mind, but I can't find the conclusions in the official style guides.

[stscicrawford]

The instructions for using Zenodo with GitHub are linked to in the section, but if you have ideas for the groups or for the categories or if you would like to add some more instructions, please do so.