close_pull_requests.yml

#/
# @license Apache-2.0
#
# Copyright (c) 2021 The Stdlib 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.
#/

# Workflow name:
name: close_pull_requests

# Workflow triggers:
on:
  pull_request_target:
    types: [opened]

# Workflow jobs:
jobs:

  # Define job to close all pull requests:
  run:

    # Define the type of virtual host machine on which to run the job:
    runs-on: ubuntu-latest

    # Define the sequence of job steps...
    steps:

      # Close pull request
      - name: 'Close pull request'
        # Pin action to full length commit SHA corresponding to v3.1.2
        uses: superbrothers/close-pull-request@9c18513d320d7b2c7185fb93396d0c664d5d8448
        with:
          comment: |
            Thank you for submitting a pull request. :raised_hands:
            
            We greatly appreciate your willingness to submit a contribution. However, we are not accepting pull requests against this repository, as all development happens on the [main project repository](https://github.com/stdlib-js/stdlib).
            
            We kindly request that you submit this pull request against the [respective directory](https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/math/base/special/havercos) of the main repository where we’ll review and provide feedback. If this is your first stdlib contribution, be sure to read the [contributing guide](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md) which provides guidelines and instructions for submitting contributions.
            
            Thank you again, and we look forward to receiving your contribution! :smiley:
            
            Best,
            The stdlib team