Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't get a simple config to work #92

Open
birkasecorba opened this issue Sep 25, 2023 · 3 comments
Open

Can't get a simple config to work #92

birkasecorba opened this issue Sep 25, 2023 · 3 comments

Comments

@birkasecorba
Copy link

Here is my config, and below that I've provided all the test diffs I tried. Any help is appreciated:

name: Merge Schedule

on:
  pull_request:
    types:
      - opened
      - edited
      - synchronize
  schedule:
    - cron: "*/30 * * * *"

permissions:
  actions: write
  checks: write
  contents: write
  deployments: write
  issues: write
  packages: write
  pull-requests: write
  repository-projects: write
  security-events: write
  statuses: write

jobs:
  merge_schedule:
    runs-on: ubuntu-latest
    steps:
      - uses: gr2m/merge-schedule-action@v2
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

and Description

test 4

/schedule 2023-09-25T18:59:23.363Z

I even got a comment from the action:
image

All the dates I've tried was in the future

permissions section was needed b/c I was getting the following error

Run gr2m/merge-schedule-action@v2
Handling pull request opened for https://github.com/birkasecorba/<repo-name>/pull/1
Error: HttpError: Resource not accessible by integration

Tests

  • Tried with 5 minutes, 15 minutes, 30 minutes, 1hour intervals. In all cases the merge time fell in those intervals and I've waited 2x the interval to make sure.
  • Tried time_zone with option with with: in yaml
  • Tried without providing any date /schedule
  • Tried with @v1
@birkasecorba
Copy link
Author

Additional information:

  • There are no other checks on the PR.
  • There are no other competing schedulers or blocking rules

@maciejwalkowiak
Copy link

Same problem here. I tried with Personal Access Token instead of Github Token - with that job runs successfully when PR is created, but fails to merge due PRs on "scheduled" action.

@gr2m
Copy link
Owner

gr2m commented Oct 23, 2023

Most likely GitHub changed something on their side that this action doesn't account for. I don't have the time to look into it myself right now I'm afraid. But I can review pull requests in case someone figures out the problem.

I just merged and released a fix that might help:
https://github.com/gr2m/merge-schedule-action/releases/tag/v2.4.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants