# Workflows for publishing Addons and updates

**URL:** <https://gramps.discourse.group/t/workflows-for-publishing-addons-and-updates/6381>\
**Category:** Development\
**Tags:** third-party-addon\
**Created:** [November 4, 2024, 7:46pm UTC](https://gramps.discourse.group/t/workflows-for-publishing-addons-and-updates/6381 "2024-11-04T19:46:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [November 4, 2024, 10:48pm UTC](https://gramps.discourse.group/t/workflows-for-publishing-addons-and-updates/6381/4 "2024-11-04T22:48:43Z")

</div>

Thanks for sharing the workflow.

> [@GaryGriffin](#):
>
> Not sure I follow. What manual burden are you referring?

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](https://gramps.discourse.group/t/what-are-your-favorite-plug-ins-which-have-not-been-distributed/4665). 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.

---

_[View the full topic](https://gramps.discourse.group/t/workflows-for-publishing-addons-and-updates/6381)._