[Initiatives.wiki] Update DevOps with Flatpak

[Carlos Soriano <csoriano src gnome org>]

commit 87ad0dc7db7c6ff2f75697627faf35721c292299
Author: Carlos Soriano <csoriano1618 gmail com>
Date:   Tue Sep 11 17:41:22 2018 +0000

    Update DevOps with Flatpak

 DevOps-with-Flatpak.md | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)
---
diff --git a/DevOps-with-Flatpak.md b/DevOps-with-Flatpak.md
index b587bd0..7b29db2 100644
--- a/DevOps-with-Flatpak.md
+++ b/DevOps-with-Flatpak.md
@@ -1,14 +1,4 @@
 # Flatpak CI
-## FAQ
-
-**Why not use the flatpak-builder one liner?**
-
-`flatpak-builder --repo=repo app org.gnome.Manifest.json`
-
-This almost does what we would want, but not quite. If you build this way it will always try to fetch your 
modules from the source specified in the manifest, but we want to use our local checkout instead. This is 
fine if you only build the `master` branch but MRs need to be able to change the source to their checkout.
-
-To achieve this we use the `--stop-at=module` argument which will build all of the dependencies up to your 
module from the manifest. Then we take over and need to install the application ourselves. This is why your 
config
-s `CONFIGURE_ARGS` variable needs to be kept in sync with your module's config options in the manifest.
 
 ### Basic building with CI
 
@@ -471,4 +461,15 @@ Then in your application window code:
 
 ```
 
-[except_master]: 
https://gitlab.gnome.org/GNOME/nautilus/blob/4ae0361342c5306ccfe1502e69bb430ac530005b/.gitlab-ci.yml#L65
\ No newline at end of file
+[except_master]: 
https://gitlab.gnome.org/GNOME/nautilus/blob/4ae0361342c5306ccfe1502e69bb430ac530005b/.gitlab-ci.yml#L65
+
+# FAQ
+
+**Why not use the flatpak-builder one liner?**
+
+`flatpak-builder --repo=repo app org.gnome.Manifest.json`
+
+This almost does what we would want, but not quite. If you build this way it will always try to fetch your 
modules from the source specified in the manifest, but we want to use our local checkout instead. This is 
fine if you only build the `master` branch but MRs need to be able to change the source to their checkout.
+
+To achieve this we use the `--stop-at=module` argument which will build all of the dependencies up to your 
module from the manifest. Then we take over and need to install the application ourselves. This is why your 
config
+s `CONFIGURE_ARGS` variable needs to be kept in sync with your module's config options in the manifest.
\ No newline at end of file