I created a GitHub release script for Omeka S module development.

For this development, I referenced the GitHub repository usage of Daniel-KM, who has developed numerous Omeka S modules.

Specifically, GitHub repositories are created with the naming convention “Omeka-S-module-{module name}”.

Example: https://github.com/Daniel-KM/Omeka-S-module-EasyInstall

For releases, they are tagged with “{module name}-{version}” and a file named “{module name}-{version}.zip” is attached.

Example: https://github.com/Daniel-KM/Omeka-S-module-EasyInstall/releases/tag/3.3.6

When this zip file is extracted, a folder named “{module name}” is created. This is necessary because Omeka S requires the module folder name to match the module name.

I created the following script to achieve this. It is intended to be run from the root of each repository.

svnr#r#z#r#g#reeaesimhmtrmpCyCpDRDseornre-ere$-i=sece$lrlelreoIiaarefeleenitt-tetaetp=ioeaepe$saeo1frhoress.Vyavtsteeti0i_hihpht.epf$eteoceo1waorosrretlezrfiefy#rhdpiyotai_s=eop_lotlpE .rspdreeax#ifaeyta#wtitr_$hmEiolhpv/pxMtre/ae$laohy$trnemd_nhsaputpa/imvllham$oeeeeetenn-rh-a$smpm$m$vioao$vereodtdreernuhuerpsllpsoie(eoisoesoinnxnint.aaat.ozmmmozrieperiyplyp_ee_pxp-afcartolthruh$/d/r$ri$enunnpangaomnmseiuei-nnt$gnove-refceyrrex_soscpimslaoautnrrdh.eye/zp$iofnpsiailm-teetosr$y-nearxmoceol-tu$)dveersi.osnh'-n"Releasedversion$version."

The gh command needs to be installed.

https://github.com/cli/cli

There may be better approaches, but I hope this is helpful for Omeka S module and theme development.