farmOS modules that involve a build step

[Symbioquine]

I recently noticed that the number of contrib modules for farmOS that I’m developing/maintaining has grown. Some of these involve a build step to produce the Javascript functionality for the module or otherwise use a workflow on GitHub before releases get pushed to Drupal.org.

Examples;

• GitHub - symbioquine/farmOS_land_drawing_tool: A land drawing tool module for farmOS - adds a tool for more quickly creating land assets.
  Builds a Vue app inside farmOS
• GitHub - symbioquine/farmOS_asset_link: Contrib module for farmOS 2.x that supercharges links to your farmOS assets with an extensible hybrid PWA experience
  Builds a PWA mobile app for farmOS which is installed/hosted under farmOS
• GitHub - symbioquine/farm_map_google: Google maps integration with farmOS
  Builds a Google Maps extension for OpenLayers and packages it as a farmOS-map behavior
• GitHub - symbioquine/drupal_jupyterlite
  Builds Jupyterlite and packages it as a Drupal module
• GitHub - symbioquine/farm_map_sjc: San Juan Islands map layers for farmOS
  No actual build step here, just doing development on GitHub and pushing releases to Drupal.org
• GitHub - symbioquine/farmOS_wfs: WFS module for farmOS
  No actual build step here, just doing development on GitHub and pushing releases to Drupal.org

I thought it might be helpful to folks (and future me) to write up how I’m using GitHub Actions to publish built Drupal modules into the Drupal.org GitLab upon each release.

See Building Drupal Modules with GitHub Actions | Symbioquine