📝 Issues when opening multiple PRs in a single workflow

In my workflow, I am attempting to use this component to open a PR to branches within the repo. I'm looking to open a PR that updates two different branches with the main branch. What actually happens, thought, is that one PR is opened and the second attempt to open a PR results in the component PATCH-ing the first PR. I expected this to open two different PRs to two different branches.

The workflow I'm using is below. I originally tried this with a matrix and had the same issue.

on: 
  workflow_dispatch:
  repository_dispatch:
    types: [update-environments]

jobs:
  continuous-integration-1:
      name: "Upper Environment Pull Requests - devex-dev"
      runs-on: ubuntu-latest
      steps:
        - name: Checkout s2-env-configuration
          uses: actions/checkout@v3
          with:
            fetch-depth: 0
  
        - name: Create pull request to s2-env-configuration devex-dev branch
          uses: devops-infra/[email protected]
          with:
            github_token: ${{ github.token }}
            allow_no_diff: true
            assignee: bentonjimmy
            source_branch: main
            target_branch: devex-dev
            title: "feat(deployment): updated devex-dev to latest s2-deployments tag"
            body: "Updated branch to latest s2-deployments tag"
            
  continuous-integration-2:
      name: "Upper Environment Pull Requests - demo-dev"
      runs-on: ubuntu-latest
      steps:
        - name: Checkout s2-env-configuration
          uses: actions/checkout@v3
          with:
            fetch-depth: 0
        - name: Create pull request to s2-env-configuration demo-dev branch
          uses: devops-infra/[email protected]
          with:
            github_token: ${{ github.token }}
            allow_no_diff: true
            assignee: bentonjimmy
            source_branch: main
            target_branch: demo-dev
            title: "feat(deployment): updated demo-dev to latest s2-deployments tag"
            body: "Updated branch to latest s2-deployments tag" ```

## :warning: Checklist
* [x] Provided a clear and concise description of what the issue is.
* [x] Given a clear and concise description of what is expected.
* [x] Proposed a clear and concise description of any alternative solutions or other features.
* [x] Added any other context or screenshots about the feature request.
* [x] Associated pull request has been already created and link was provided.


*Check [CONTRIBUTING.md][contributing] and [CODE_OF_CONDUCT.md][code] for more information*

[contributing]: https://github.com/devops-infra/.github/blob/master/CONTRIBUTING.md
[code]: https://github.com/devops-infra/.github/blob/master/CODE_OF_CONDUCT.md

📝 Brief description

Recent PRs that have been created by this bot always seem to have some weird symbols appearing in them. An example of most recent such PR can be seen here: livepeer/catalyst#247

as you see, the description of the PR is:

livepeer/catalyst@6941d0f - livepeer-docker - 2022-11-07 12:40:15 ^NowALiNiA^ [AUTO-COMMIT] Update manifest.yaml^NowALiNiA^ Files changed:^NowALiNiA^M manifest.yaml

where i've no clue about the text ^NowALiNiA^ appearing in it. The workflow file is available at: https://github.com/livepeer/catalyst/blob/main/.github/workflows/staging.yaml

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

📝 Brief description

When I add more than 1 user (see code below) as reviewer the action doesn't add any. I would like to add multiple users to review the pull request.

• is it possible to add multiple reviewers ?
• is there a syntax error in my code?

- name: Create pull request
        uses: devops-infra/[email protected]
        with:
          github_token: ${{ secrets.AUTOMATISATION }}
          target_branch: uat
          title: "[AUTO] PR title"
          template: path to PR template.md
          reviewer: username1, username2, username3
          label: automated workflow
          get_diff: false

Description

Running the Action at the latest version (0.5.5) runs into an error. While GH shows an error, the PR is correctly created and visible in the PR view on GH. This step is the last in my workflow, so not critical at the moment, but it is not exactly helpful when a workflow run always shows as failed while it actually achieved what it should have.

Details

Error in the log (last two lines in the job's log):

Error updating issue: Unprocessable Entity (HTTP 422)
Invalid value for "name"

Job configuration in the workflow:

- name: Create Release PR
        id: create-pull-request 
        uses: devops-infra/[email protected]
        with:
          github_token: ${{ github.token }}
          target_branch: 'master'
          source_branch: 'release-${{ steps.timestamp.outputs.time }}'
          title: '[RELEASE] Create a new Release'
          body: Auto-generated by the _Create Release PR_ Action
          label: automated pr, release
          assignee: 7tupel

The output referenced in source_branch is correctly set and is correctly used by the action to create the PR.

My repository is public and available here: https://github.com/ClockworksIO/clci

📝 fatal: unsafe repository ('/github/workspace' is owned by someone else)

Same issue as gaurav-nelson/github-action-markdown-link-check#132 .
From the recent commit to master it looks like you guys are already aware of this, but the fix doesn't seem to be working yet.

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

Brief description

Replace some predefined text with commit message.
Include all commits from the pull request.

Additional information

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md for more information

📝 Brief description

We merge everything to develop. Once a week we merge everything from develop to master. This weekly master merge contains 50+ commits from 10+ issues with 10+ pull requests. In our weekly master merge we want a description with all the related issues or related PRs. I tried different actions, tools or ways to do that. Now Im trying to use your action (which we already use for the weekly master merge). I tried using different actions where the output should be the related PRs and use this output in the body of your action. I tried using different outputs (url or PR number) of your action but nothing seems to work. Im pretty new to all of this but for my understanding im doing everything correctly. Once again, I tried a bunch of different things... The body is just always empty when I look into the logs. Is it a bug? Am I doing something wrong? Is it outdated? Here is a screenshot of my action:

This is a test repository with a PAT with most of the permissions. Im just trying to change the body. The comments are some things I tested before but they didnt work either.

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

📝 Brief description

So I have been merrily using this action to create a PR whenever there is a push to our develop branch with this bit of yaml I think I took from the main page here:

      - name: Run the action
        uses: devops-infra/[email protected]
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          source_branch: develop
          target_branch: release/MAPL-v3
          label: automatic,MAPL3,Skip Changelog
          template: .github/PULL_REQUEST_TEMPLATE/auto_pr_to_mapl3.md
          get_diff: true
          assignee: ${{ github.actor }}
          old_string: "<!-- Write your description here -->"
          new_string: ${{ github.event.commits[0].message }}
          title: Auto PR - develop → MAPL-v3 - ${{ github.event.commits[0].message }}

But in the last couple of days the action has been failing (example) with:

/entrypoint.sh: line 127: /usr/bin/sed: Argument list too long

and it seems like this:

got too long. This MAPL3 branch is a very long lived development branch (development on top of develop) and so I can imagine we might finally be blowing it out.

Now, we don't actually use the commits bit from line 127 in our template:

## :memo:  Automatic PR: `develop` → `release/MAPL-v3`

### Description

<!-- Write your description here -->

## :file_folder:  Modified files
<!-- Diff files - START -->
<!-- Diff files - END -->

to make PRs like GEOS-ESM/MAPL#2212 so this explains why I've never seen commits in them, but I do like seeing the files that changed.

Is there anything I can do to "bypass" the commit-diff? Or do I need to just go full get_diff: false from now on? (And if so, what does the automatic PR then look like...)

Or, perhaps, if desired, would you be amenable to a PR that did finer grained get_diff options (e.g., git_diff_commits or something?) I can maybe see how to do it but GitHub Actions are also pretty mysterious to me. 😄

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

Im using the below actions in one of the workflow

  - name: Create PR
    #if: startsWith(github.ref, 'refs/heads/feature')
    uses: devops-infra/[email protected]
    with:
      github_token: ${{ secrets.GITHUB_TOKEN }}
      title: ${{ github.event.commits[0].message }}
      assignee: ${{ github.actor }}
      label: automatic,feature
      # template: .github/PULL_REQUEST_TEMPLATE/FEATURE.md
      old_string: "**Write you description here**"
      new_string: ${{ github.event.commits[0].message }}
      get_diff: true
      target_branch: main

in the same repo i have another workflow which triggers when the pull request is created to main

  name: secondworflow.yaml
   on: 
    push:
      branches: [ main ]
    pull_request_target:
      types: [assigned, opened, synchronize, reopened]
      branches:
        - main
        - 'release/**'
    workflow_dispatch:
  
  permissions:
    id-token: write
    contents: read
    issues: write
    pull-requests: write
      
  jobs:
    build:
      *********

manually creating pull request to main is triggering the seconfworflow, but the PR's which are created using this action is not triggering,

📝 Brief description

Hi,

I am getting the message "Branches are the same" even though they are different.
I have a feature branch that is one commit ahead and a master which is also one commit ahead.

Comparing branches by diff...
fatal: remotes/origin/master...remotes/origin/automatic-sync: no merge base

[INFO] Both branches are the same. No action needed.

I believe this line is checking for a diff between the branches, which will result in a 0 if both are ahead by one, instead, I think it should be checking for only feature branch.

Brief description

Getting new commits in the source branch
fatal: ambiguous argument 'origin/master origin/rymek-ro-master..origin/feature/budget': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

New branch cannot have master in its name.

Checklist

• Provided a clear and concise description of what the bug is.
• Given a clear and concise description of what was expected to happen.
• Provided an information how to reproduce the error.
• If applicable, added screenshots to help explain the issue.
• Added any other context about the issue that can help to understand it.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md for more information

📝 Brief description

It would be nice if we could specify a different repo than the one on the workflow, like this action can

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

If you create/edit a pull request manually and add a closing statement in the pull request body the pullRequest.closingIssuesReferences is updated.

When creating/editing a pull request with this action these closingIssuesReferences are not updated and therefore the issues will not be closed if the pull request is merged.

My workflow: PR to beta -> PR is merged to beta -> this action is executed and adds all issues mentioned in the PR with a closing statement to a new/existing PR to main -> PR to main is merged for release but issues are not closed because they are not contained in the closingIssuesReferences (Development bottom right)

The pull request was edited after the first 2 closing statements were added by this action. Therefore these 2 issues are linked in the section Development. For the last 2 issues the body PR to main was updated by the action but they are not linked in the closingIssuesReferences section (Developement).

Brief description

Pull requests created by Dependabot produce execution errors.

Listing new commits in the source branch...
* 624917e - dependabot[bot] - 2021-04-26 11:27:21 
  Bump urllib3 from 1.26.2 to 1.26.4 in /backend Bumps [urllib3](https://github.com/urllib3/urllib3) from 1.26.2 to 1.26.4.
  - [Release notes](https://github.com/urllib3/urllib3/releases)
  - [Changelog](https://github.com/urllib3/urllib3/blob/main/CHANGES.rst)
  - [Commits](https://github.com/urllib3/urllib3/compare/1.26.2...1.26.4)
  
  Signed-off-by: dependabot[bot] <[email protected]>

Listing commits subjects in the source branch...
Bump urllib3 from 1.26.2 to 1.26.4 in /backend

Listing files modified in the source branch...
 backend/requirements.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Setting template...
Aborted: could not find any git remote pointing to a GitHub repository

Checklist

• Provided a clear and concise description of what the bug is.
• Given a clear and concise description of what was expected to happen.
• Provided an information how to reproduce the error.
• If applicable, added screenshots to help explain the issue.
• Added any other context about the issue that can help to understand it.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md for more information

📝 Brief description

Inputs:
  source_branch: 
  target_branch: develop
  title: Bump for tf-1.0.9-tg-0.35.4
  template: .tmp/PULL_REQUEST_TEMPLATE.md
  body: 
  reviewer: 
  assignee: ChristophShyper
  label: automatic,dependency
  milestone: 
  draft: false
  get_diff: true
  old_string: 
  new_string: 
  ignore_users: dependabot

Setting GitHub credentials...

Setting branches...
Source branch: dependency/tf-1.0.9-tg-0.35.4
Target branch: develop

Updating all branches...
From https://github.com/devops-infra/docker-terragrunt
 * [new branch]      automatic  -> automatic

Comparing branches by revisions...

Comparing branches by diff...
fatal: ambiguous argument 'remotes/origin/develop...remotes/origin/dependency/tf-1.0.9-tg-0.35.4': unknown revision or path not in the working tree.

Use '--' to separate paths from revisions, like this:
[INFO] Both branches are the same. No action needed.
'git <command> [<revision>...] -- [<file>...]'

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

📝 Brief description

description of what the issue is.

The action only has an output of url (pull request url)
If you want to perform additional additional actions after this action it is very helpful to know the number of the pull request, not the full URL. (For my use-case I want to run peter-evans/enable-pull-request-automerge@v2 afterwards)

description of what is expected.

An additional output to be provided, with name pull-request-number

description of any alternative solutions or other features.

For now I am taking the pull request url, and parsing the pull request number from it. Not a dealbreaker, but a bit fiddly to do.
Plus if the url scheme for github pull requests ever changes, I'd have to adjust my logic

Here's what I'm doing to extract the PR number

- name: Get Pull Request Number
        id: prNumber
        run: |
          regex="\/pull\/([0-9]+)"
          if [[ ${{ steps.create-pull-request.outputs.url }} =~ $regex ]]
              then
                  echo "::set-output name=prNumber::${BASH_REMATCH[1]}"
              else
                  echo "$pullRequestNumber is not valid" >&2
              fi

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

📝 Hello, just wondering if anyone here had the need to attach a body file instead of list of commits as described in the readme. Is there a way to pass in the file location for the body?

Thanks a lot!

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

📝 Brief description

Enable auto merge on the newly created PR when all checks are met

That would simplify the pipeline management

Would it be too hard or out of scope to add this feature?

📝 Brief description

Hi, i'm trying to add the team as a reviewer but is not picking it up

I've tried reviewer: "team-prs" reviewer: "/team-prs" reviewer: "@org/team-prs" reviewer: "org/team-prs"

and it shows an error Error requesting reviewer: Unprocessable Entity (HTTP 422)

expected to pick up one of the members of the team to review

any ideas?

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

📝 Brief description

I'm currently using this cool action to try and automate some processes for a code I work on. And so far, so good. But on this repo we have a changelog enforcer action as well but for the auto PRs I'd like to "skip" the changelog enforcer as in this case, I don't care.

That said, I seem to be dumb at trying to do this. The label is "Skip Changelog" and I added to my yaml:

          label: automatic,MAPL3,"Skip Changelog"

But, when I tried it out in a tester repo, the action applied just "Skip":

mathomp4/labeltest#35

What is the correct way to handle labels with spaces in them?

⚠️ Checklist

• Provided a clear and concise description of what the issue is.
• Given a clear and concise description of what is expected.
• Proposed a clear and concise description of any alternative solutions or other features.
• Added any other context or screenshots about the feature request.
• Associated pull request has been already created and link was provided.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information