How to set up a plugin to use Git Updater?
I'm a plugin author, and have some users who want to use Git Updater rather than the w.org repo to update my stuff.
I'm looking for some "here's what you do, plugin author" documentation on this, and I'm coming up short.
Reading between the lines of the Git Updater documentation, it looks to me like installing a plugin with Git Updater copies the entire contents of the Primary branch: whatever header it finds in the main plugin file (or theme style.css).
And updating it compares the Version: 1.2.3 headers in the presently installed plugin and the Github (or Gitlab &c) repo.
It looks like Git Updater, unlike the w.org repo svn setup, doesn't use the Version 1.2.3 header to decide which tagged version to install. And unlike 10up's CI workflows, it looks like Git Updater doesn't honor .distignore, so it pulls unit tests and other build-time assets as well as runtime.
Is there a commonly accepted way of setting up for Git Update? Does anybody have any guidelines for that? Ideally, it would do more-or-less what the w.org repo does with tags. But I'll be happy with any convention that lots of people follow.
Thanks.