Product updates

Historically, Spacelift was only able to handle one VCS integration per type. Not anymore! Take a look at our new approach to handle version control systems.

The VCS settings have moved from the Settings page to the left sidebar under Source code menu, and the following new features have been added:

• No limitations on the number of VCS integrations. For instance, you can have 10 GitHub and 5 GitLab integrations at the same time. Note that you can create multiple integrations pointing to the same VCS as well.
• Two integration types: default and Space-level. Default integrations are accessible by everyone (same as before), while Space-level integrations are controlled by Space access controls. Note: all existing integrations have been marked as default integrations.
• Fine-grained access control. Have any repositories that should only be available to certain people or teams? Use Space-level integrations! When a VCS integration is tied to a Space, the stack Space needs to have access to the integration Space, similarly to any other Space-level entity such as Policies, Contexts, Cloud Integrations.
• The VCS details (id, name, labels, description, Space, is default) have been added to the Push policy input.
• You can organize your integrations with custom names, labels and descriptions.