[gnome-builder/wip/gtk4-port] plugins/buildui: add export build menu item

[Christian Hergert <chergert src gnome org>]

commit 5a19a3499e969b53eee941cc34167407c5df7c57
Author: Christian Hergert <chergert redhat com>
Date:   Mon May 2 12:05:54 2022 -0700

    plugins/buildui: add export build menu item
    
    We still probably want to drop the "Generic" export feature and instead go
    to configuration-backed export support. Another option would be for the
    flatpak-builder plugin to use create a specialized pipeline which can
    produce a non-incremental build using flatpak-builder without --stop-at
    or anything like that (yet preserving cachepoints).

 src/plugins/buildui/gtk/menus.ui | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)
---
diff --git a/src/plugins/buildui/gtk/menus.ui b/src/plugins/buildui/gtk/menus.ui
index 36f1c9f65..e93868926 100644
--- a/src/plugins/buildui/gtk/menus.ui
+++ b/src/plugins/buildui/gtk/menus.ui
@@ -58,6 +58,17 @@
         <attribute name="action">build-manager.clean</attribute>
       </item>
     </section>
+    <section id="build-export">
+      <item>
+        <!-- TODO: Instead of having a generic Export via the build-manager,
+          this should move into the Flatpak plugin and have it use
+          flatpak-builder directly (reusing our cachepoints) so that
+          the output is the same as using flatpak-builder from Flathub, etc.
+        -->
+        <attribute name="label" translatable="yes">_Export</attribute>
+        <attribute name="action">build-manager.export</attribute>
+      </item>
+    </section>
     <section id="build-cork">
       <item>
         <attribute name="label" translatable="yes">Stop Build</attribute>
@@ -86,7 +97,6 @@
         <attribute name="action">foundryui.manage-sdks</attribute>
       </item>
     </section>
-    <section id="build-export"/>
   </menu>
   <menu id="run-menu">
     <section id="run-command-section">