The problem with tagging the report is similar to what happened here. The report had TWO different items: a Gramplet prototype and a change to a module.
The PR @Nick-Hall referenced covers the exportgedcom.py
But that leaves the AncestryGramplet still marooned. And while Notes with text have a permalink generated automatically, the Notes that are only attachments do not.
In that particular case, Sam posted an experimental gramplet in ADDITION to the patched GEDCOM export module from Tom Samstag’s AncestryCitations repository. Which is discussed in the “Gramps and Ancestry hints” thread of the Gramps Users maillist.
With the new “experimental/Beta” statuses and “Expert/Developer” audiences filters being introduced, it is reasonable to actively recruit and post even risky addons … maybe to a separate location than the addons-source repository. Developers should be more willing to post their contributions in the Gramps-project GitHub space, indicating it is FULLY in Open-Source and others are welcome to fork it. (Even though Tom embedded the GNU GPLv2 license in the source posted to his public repository, I’m betting a lot of us still feel like we need permission to play with that code.)