Lines Matching full:pr
115 self.pr = self.repo.get_issue(pr_number).as_pull_request()
116 self._team_name = "pr-subscribers-{}".format(
119 self.COMMENT_TAG = "<!--LLVM PR SUMMARY COMMENT-->\n"
122 for comment in self.pr.as_issue().get_comments():
140 diff_stats = f"{self.pr.changed_files} Files Affected:\n\n"
141 for file in self.pr.get_files():
156 patch = requests.get(self.pr.diff_url).text
160 patch_link = f"Full diff: {self.pr.diff_url}\n"
162 patch_link = f"\nPatch is {human_readable_size(len(patch))}, truncated to {human_readable_size(DIFF_LIMIT)} below, full version: {self.pr.diff_url}\n"
166 body = escape_description(self.pr.body)
173 Author: {self.pr.user.name} ({self.pr.user.login})
194 self.pr.as_issue().create_comment(comment)
217 self.pr = repo.get_issue(pr_number).as_pull_request()
220 # We assume that this is only called for a PR that has just been opened
227 Thank you for submitting a Pull Request (PR) to the LLVM Project!
229 This PR will be automatically labeled and the relevant teams will be notified.
235 If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.
239 You can also ask questions in a comment on this PR, on the [LLVM Discord](https://discord.com/invite/xS7Z362) or on the [forums](https://discourse.llvm.org/)."""
240 self.pr.as_issue().create_comment(comment)
249 self.pr = repo.get_issue(pr_number).as_pull_request()
253 # As soon as a new contributor has a PR merged, they are no longer a new contributor.
255 # added a new contributor greeting comment when they opened the PR.
257 for comment in self.pr.as_issue().get_comments():
264 # revision that the PR was merged on to, beyond that it's closed forever.
277 @{self.author} Congratulations on having your first Pull Request (PR) merged into the LLVM Project!
279 Your changes will be combined with recent changes from other authors, then tested by our [build bots](https://lab.llvm.org/buildbot/). If there is a problem with a build, you may receive a report in an email or a comment on this PR.
283 How to do this, and the rest of the post-merge process, is covered in detail [here](https://llvm.org/docs/MyFirstTypoFix.html#myfirsttypofix-issues-after-landing-your-pr).
285 If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of [LLVM development](https://llvm.org/docs/DeveloperPolicy.html#patch-reversion-policy). You can fix your changes and open a new PR to merge them again.
289 self.pr.as_issue().create_comment(comment)
482 def pr_request_review(self, pr: github.PullRequest.PullRequest):
492 for commit in pr.get_commits():
502 message = "{} What do you think about merging this PR to the release branch?".format(
505 pr.create_issue_comment(message)
506 pr.create_review_request(reviewers)
567 print("PR already exists...")
633 pr = repo.get_issue(pr_number).as_pull_request()
634 submitter = pr.user.login
636 m = re.search("Requested by: @(.+)$", pr.body)
646 comment = f"{mention} (or anyone else). If you would like to add a note about this fix in the release notes (completely optional). Please reply to this comment with a one or two sentence description of the fix. When you are done, please add the release:note label to this PR. "
648 pr.as_issue().create_comment(comment)
672 pr_subscriber_parser = subparsers.add_parser("pr-subscriber")
676 pr_greeter_parser = subparsers.add_parser("pr-greeter")
679 pr_buildbot_information_parser = subparsers.add_parser("pr-buildbot-information")
727 "--pr-number",
741 elif args.command == "pr-subscriber":
746 elif args.command == "pr-greeter":
749 elif args.command == "pr-buildbot-information":