setup-scm
Introduction
The setup-scm Action creates and configures a source code repository to receive workflow execution triggers, enabling integration with the StackSpot platform.
Key Features of the Action:
- Configuration of repositories for integration with StackSpot.
- Support for multiple source control management (SCM) providers, including Azure, Bitbucket, GitHub, and GitLab.
- Automating configuration parameters such as access tokens, project names, organizations, and repositories.
- Ability to support specific configurations for on-premise providers like GitLab.
How to use the Action
1. Running the Action
In the terminal, run the following command to start the Action:
stk run action stackspot-core/setup-scm@1.0.0
2. Action Inputs
During execution, you will be prompted for the following inputs, depending on the SCM provider selected:
| Field | Description | Required for |
|---|---|---|
| SCM provider | SCM provider. Options: Azure, Bitbucket, Github, and Gitlab. | All |
| Personal Access Token | Personal Access Token. | Azure, Github, and GitLab |
| Project Name | Project name. | Azure and GitLab |
| Project Key | Project key. | Bitbucket |
| Organization Name | Organization Name. | Azure and Github |
| Repository Name | Repository name. | Github, Bitbucket, and Azure |
| Group Name | Group name. | GitLab |
| Is on premise? | Indicates whether the GitLab provider is on-premise. | GitLab |
| Workspace Name | Workspace name. | Bitbucket |
| Client Key | Client key. | Bitbucket |
| Client Secret | Client secret. | Bitbucket |
| Gitlab api domain | GitLab API domain (default: gitlab.com). | GitLab on-premise |
After filling in the fields, the Action will automatically configure the repository for integration with StackSpot.