Create PR on Schedule (like every monday 8:00 am)

[JigarM]

Can we create a new PR from specific branch on schedule?
My requirement is need to create auto PR from develop to master on every week/specific day.

on:
  schedule:
    - cron: '0 8 * * MON'
jobs:
  createPullRequest:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Create Pull Request
        id: cpr
        uses: peter-evans/create-pull-request@v2.4.4
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          commit-message: Merge development to master
          title: '[Example] Add report file'
          body: |
            Auto-generated PR to make sure our `master` branch should have the latest code 
          labels: ready for review
          assignees: JigarM
          reviewers: JigarM
          branch: develop

[peter-evans]

@JigarM You can do that, yes. Please see this example.

Here is what that pattern would look like for your workflow. It checks out master, resets to develop, and then creates a PR to merge into master. The PR branch is named master-promotion (you can rename it to whatever you want, but don't use an existing branch).

    steps:
      - uses: actions/checkout@v2
      - name: Reset promotion branch
        run: |
          git fetch origin develop:develop
          git reset --hard develop
      - name: Create Pull Request
        id: cpr
        uses: peter-evans/create-pull-request@v2.4.4
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          commit-message: Merge development to master
          title: '[Example] Add report file'
          body: |
            Auto-generated PR to make sure our `master` branch should have the latest code 
          labels: ready for review
          assignees: JigarM
          reviewers: JigarM
          branch: master-promotion

[JigarM]

@peter-evans Thanks for the quick response. Let me try this way.
I did the mistake to set the PR branch name with existing branch. I hope it should work. Will update you here.

Thanks anyway.!!!

[JigarM]

@peter-evans Below changes works fine for me.

name: Create Pull Request
on:
  push:
  schedule:
    - cron: '0 8 * * MON'
jobs:
  createPullRequest:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
        with:
          ref: master
      - name: Reset develop branch
        run: |
          git fetch origin develop:develop
          git reset --hard develop
      - name: Create Pull Request
        id: cpr
        uses: peter-evans/create-pull-request@v2.4.4
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          commit-message: Merge `development` to `master`
          title: Merge develop to master
          body: |
            Auto-generated PR to make sure our master branch should have the latest code 
          labels: ready for review
          branch: develop-promotion
      - name: Check outputs
        run: |
          echo "Pull Request Number - ${{ env.PULL_REQUEST_NUMBER }}"
          echo "Pull Request Number - ${{ steps.cpr.outputs.pr_number }}" 

Thanks for the help!!!!

[JigarM]

@peter-evans One more thing I want to share. Github action can't trigger the workflow on schedule time. such as when I write this, nothing happens.

on:
  schedule:
    - cron: '0 8 * * MON'

But when I add push, the action triggered on push

on:
  push:
  schedule:
    - cron: '0 8 * * MON'

So, how we can schedule without "push" call?

[peter-evans]

Maybe MON isn't an accepted way to set the cron schedule. Try using digits to set the day instead.

on:
  schedule:
    - cron: '0 8 * * 1'

[JigarM]

@peter-evans That's not an issue. Even I tried cron: "*/2 * * * *" but still its not working.
YML is not calling at every 2 minutes.

That's why I need to add push in the yml.

[JigarM]

Do I need to update the yml with PAT(Personal access token)?

[peter-evans]

You can't schedule it every 2 minutes. The shortest is 5.

The shortest interval you can run scheduled workflows is once every 5 minutes.

https://help.github.com/en/actions/reference/events-that-trigger-workflows#scheduled-events-schedule

Also, make sure the workflow is in the master (default) branch. It won't trigger otherwise.

Do I need to update the yml with PAT(Personal access token)?

No, this is not necessary for your use case.

[JigarM]

Got it!!!
@peter-evans Thanks for correcting me. Changes runs fine now.
Thanks for everything..