Thanks for sharing the workflow.
The normal workflow is addon contributors submitting Pull Requests via a gramps-project/addons-source clone on the GitHub domain or the GitHub Desktop app. Then an authorized contributor validating their Pull Request and committing the change.
The manual processes (for publishing a NEW addon) have several different approaches:
- submitting by eMail or Discourse Private Messaging
- requesting help publishing an addon from a GitHub repository (that isn’t in a cloned)
- code shared in an MantisBT issue
There is a thread with a sampling of plug-ins that are not yet published. So it would good to establish workflows that enable some approaches … without making it onerous (or error prone) for either the contributor or the volunteer.