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

292: Add comment to PR when it becomes outdated #513

wants to merge 2 commits into from


Copy link

@rwestberg rwestberg commented Mar 17, 2020

Hi all,

Please review this change that posts an instructional message on how to sync with the target branch the first time a PR is marked as outdated.

Best regards,


  • Change must not contain extraneous whitespace
  • Change must be properly reviewed


  • SKARA-292: Add comment to PR whent it becomes outdated


  • Erik Helin (ehelin - Reviewer) ⚠️ Review applies to 0a14874


$ git fetch pull/513/head:pull/513
$ git checkout pull/513

Copy link

@bridgekeeper bridgekeeper bot commented Mar 17, 2020

👋 Welcome back rwestberg! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request.

Copy link

@mlbridge mlbridge bot commented Mar 17, 2020


edvbld approved these changes Mar 18, 2020
Copy link

@edvbld edvbld left a comment

Looks good, just a small nit regarding the comment!

Copy link

@openjdk openjdk bot commented Mar 18, 2020

@rwestberg This change now passes all automated pre-integration checks. When the change also fulfills all project specific requirements, type /integrate in a new comment to proceed. After integration, the commit message will be:

292: Add comment to PR when it becomes outdated

Reviewed-by: ehelin
  • If you would like to add a summary, use the /summary command.
  • To credit additional contributors, use the /contributor command.
  • To add additional solved issues, use the /solves command.

Since the source branch of this PR was last updated there has been 1 commit pushed to the master branch. Since there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge master into your branch, and then specify the current head hash when integrating, like this: /integrate c0abd82e75b2cd1c34b46acbc27b9e255e2cd788.

➡️ To integrate this PR with the above commit message, type /integrate in a new comment.

@openjdk openjdk bot added the ready label Mar 18, 2020
Co-Authored-By: Erik Duveblad <>
Copy link
Member Author

@rwestberg rwestberg commented Mar 18, 2020


@openjdk openjdk bot closed this Mar 18, 2020
@openjdk openjdk bot added the integrated label Mar 18, 2020
Copy link

@openjdk openjdk bot commented Mar 18, 2020

@rwestberg The following commits have been pushed to master since your change was applied:

  • c0abd82: 317: git-webrev uses wrong JBS links for commit messages

Your commit was automatically rebased without conflicts.

Pushed as commit 4b7b969.

Copy link

@mlbridge mlbridge bot commented Mar 18, 2020

Mailing list message from Robin Westberg on skara-dev:

Changeset: 4b7b969
Author: Robin Westberg <rwestberg at>
Date: 2020-03-18 09:49:47 +0000

292: Add comment to PR when it becomes outdated

Reviewed-by: ehelin

! bots/pr/src/main/java/org/openjdk/skara/bots/pr/
! bots/pr/src/test/java/org/openjdk/skara/bots/pr/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants