Adding usage of content-type header in one of http examples #1566
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Copyright 2020 The Serverless Workflow Specification Authors | |
# | |
# Licensed under the Apache License, Version 2.0 (the "License"); | |
# you may not use this file except in compliance with the License. | |
# You may obtain a copy of the License at | |
# | |
# http://www.apache.org/licenses/LICENSE-2.0 | |
# | |
# Unless required by applicable law or agreed to in writing, software | |
# distributed under the License is distributed on an "AS IS" BASIS, | |
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
# See the License for the specific language governing permissions and | |
# limitations under the License. | |
# This workflow will triage pull requests and apply a label based on the | |
# paths that are modified in the pull request. | |
# | |
# To use this workflow, you will need to set up a .github/labeler.yml | |
# file with configuration. For more information, see: | |
# https://github.com/actions/labeler/blob/master/README.md | |
name: Labeler | |
on: [pull_request] | |
jobs: | |
label: | |
runs-on: ubuntu-latest | |
steps: | |
- uses: actions/labeler@v2 | |
with: | |
repo-token: "${{ secrets.GITHUB_TOKEN }}" |