-
Notifications
You must be signed in to change notification settings - Fork 615
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
Re-running review when PR is synchronized #504
Comments
This is currently supported only in GitHub App |
@nataliezeller1
|
Thanks @ken109 |
@nataliezeller1 |
Thanks @mrT23
The pr-agent is still not triggered when new code is pushed to an open PR. I can see this message in the logs: |
@nataliezeller1 for example:
you need to define which tools will run each push. if it still doesn't work, please send a full og |
@mrT23 yes I included the push_commands and it didn't help. |
"I've tried to install it using github app, and set the following in a pr_agent.toml file under the root of my repo:" .pr_agent.toml Without a full log, I cannot understand if there are other problems. |
yes there is a dot at the beginning of the file - .pr_agent.toml |
@nataliezeller1 did you enable push events in the app settings? |
@okotek we tried to enable push events in the app, but it still ignores them (although we set handle_push_trigger=true in the configuration file in the repo).
|
@nataliezeller1
Make sure the file is in the root of the repo's main branch prior to creating a PR. |
yes the other configurations in this file are reflected, just not the handle_push_trigger. |
@nataliezeller1 I have identified an issue with 'synchronize' events in GithubApp, and opened a PR to fix it: |
Thanks for handling this so quickly! |
@nataliezeller1 we merged #511 |
@mrT23 It works, thanks! |
I'm running the pr-agent as a git action. When a PR is opened, the review is running and a comment is added.
Is there a way to re-run review automatically also when the PR gets synchronized with additional commits?
The text was updated successfully, but these errors were encountered: