With raw kube approach, we can easily have a built-in ComponentDefinition to reference a Git repo as a component (using Flux Kustomization as example but there're many approaches indeed):

apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
  name: foo
  namespace: default
spec:
  workload: 
    definition: 
      apiVersion: apps/v1
      kind: Deployment # 

Is your feature request related to a problem? Please describe.
In case feature branches and merges are used to update the spacegun configuration, it might be nice to have an automated way to "lint" the new spacegun config before submitting it.

Describe the solution you'd like
A command line switch for one of the spacegun tools (probably standalone) should exist, that makes spacegun re