step.yml

#
# A couple of useful guides & docs:
#
# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs
# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md
# - Bitrise docs: http://devcenter.bitrise.io/
# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/

title: |-
  Github release
summary: |
  Step for creating an release on the current Github repository.
description: |
  Create a release on Github. Add changelog and binaries.
website: https://github.com/AndroidGuyDD/lovoo/bitrise-step-github-release
source_code_url: https://github.com/AndroidGuyDD/lovoo/bitrise-step-github-release
support_url: https://github.com/AndroidGuyDD/lovoo/bitrise-step-github-release/issues
host_os_tags:
  - osx-10.10
  - ubuntu-16.04

# If this step should be available only for certain project types
# just uncomment this `project_type_tags` section and include all the
# project types supported by the step. If the step can be used for all
# project types then you can just remove this section.
# If no `project_type_tags` specified (or specified as an empty array)
# that means the step can be used for any project type.
# You can find more information about project type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
#
# project_type_tags:
#   - ios
#   - macos
#   - android
#   - xamarin
#   - react-native
#   - cordova
#   - ionic

# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
  - utility

is_requires_admin_user: false
is_always_run: false
is_skippable: false
run_if: ""

deps:
  brew:
  - name: git
  - name: wget
  apt_get:
  - name: git
  - name: wget

toolkit:
  go:
    package_name: github.com/lovoo/bitrise-step-github-release

inputs:
  - github_auth_token: ""
    opts:
      title: "GitHub auth token"
      summary: ""
      description: |-
        Authorization token for GitHub applications
        You can create one for yourself at the following url:
        [https://github.com/settings/tokens](https://github.com/settings/tokens)

        Add repo and public_repo scope to the generated token, to allow to creating releases tp private repos and public repos respectively.
      is_expand: true
      is_required: true
  - repository_url: "$GIT_REPOSITORY_URL"
    opts:
      title: "Repository URL"
      summary: ""
      description: |-
        The URL for the repository we are working with
      is_required: true
      is_expand: true
  - changelog_file_list: ""
    opts:
      title: "List of files that contain change notes"
      summary: ""
      description: |-
        Specify file(s) which contain change notes and seprate with | symbol when added more than one file path
      is_required: true
  - release_tag: "$BITRISE_BUILD_NUMBER"
    opts:
      title: "The name of the tag, which will be created on the current branch"
      summary: ""
      description: |-
        Specify a name for the tag.
      is_required: true
  - release_name: "release_$BITRISE_BUILD_NUMBER"
    opts:
      title: "The name of release"
      summary: ""
      description: |-
        Specify a name for the release (will be used as the headline). 
      is_required: true
  - target_commitish: ""
    opts:
      title: "Branch name or commit hash"
      summary: ""
      description: |-
          Specifies the commitish value that determines where the Git tag is created from. Can be any branch or commit SHA.
      is_required: false
  - is_draft: "false"
    opts:
      title: "Is the release a draft?"
      summary: ""
      description: |-
        If it's a draft, set to `true`.
      is_required: false
      value_options:
      - "true"
      - "false"
  - is_prerelease: "false"
    opts:
      title: "Is it a prerelease"
      summary: ""
      description: |-
        If it's a prerelease, set to `true`
      is_required: false
      value_options:
      - "true"
      - "false"
  - upload_asset_file: ""
    opts:
      title: "The file that should be attached to this release as asset."
      summary: ""
      description: |-
        Specify the relative path from your project root for the file that should be uploaded as asset for this release. 
      is_required: false

outputs:
  - RELEASE_URL:
    opts:
      title: "The link to the created GitHub release"
      summary: ""
      description: |
        URL of the created release on Github.