Improve consistency of issue templates

The content to be replaced is now on the same line for (Azure Devops, CircleCI and Jenkins). Since we expect values to be on the same line as the attributes, some templates were putting into on different line which might confuse users

Issue templates for different providers are more consistent with similar wording for the inputs
This commit is contained in:
Tiago Pascoal
2023-01-12 18:19:24 +00:00
committed by GitHub
parent b6985e7dd4
commit fba0aa5993
5 changed files with 6 additions and 11 deletions

View File

@@ -10,11 +10,8 @@ assignees: ""
Provide the following required inputs:
Organization:
_The Azure DevOps organization to migrate pipelines from._
Project:
_The Azure DevOps project to migrate pipelines from._
Organization: _Replace this text with the Azure DevOps organization to migrate pipelines from._
Project: _Replace this text with the Azure DevOps project to migrate pipelines from._
## Available commands

View File

@@ -10,7 +10,7 @@ assignees: ""
Provide the following required inputs:
Organization: _The CircleCI organization to migrate pipelines from._
Organization: _Replace this text with the CircleCI organization to migrate pipelines from._
## Available commands

View File

@@ -10,7 +10,7 @@ assignees: ""
Provide the following **required** inputs:
Namespace: **Replace this text with the GitLab namespace (or group) to migrate pipelines from.**
Namespace: _Replace this text with the GitLab namespace (or group) to migrate pipelines from._
## Available commands

View File

@@ -10,8 +10,7 @@ assignees: ""
Provide the following optional inputs:
Folders:
_Include specific folders in an audit_
Folders: _Include specific folders in an audit (delete if not applicable)_
## Available commands

View File

@@ -10,8 +10,7 @@ assignees: ""
Provide the following required inputs:
Organization:
_The Travis CI organization to migrate pipelines from._
Organization: _Replace this text with the Travis CI organization to migrate pipelines from._
## Available commands