[Github] Improve formating of PR diffs in bot notifications (#66118)

* This avoid pinging folks on all issue when they got pinged on bugzilla
eons ago
* Avoid formatting bugs when there is html in

[Github] Improve formating of PR diffs in bot notifications (#66118)

* This avoid pinging folks on all issue when they got pinged on bugzilla
eons ago
* Avoid formatting bugs when there is html in the issue description
* Truncate the list of files and the diff independently of each other.
This avoids truncating cutting a file line in 2 and to cut in the middle
of html markup. This is a fringe case but it does happen when people
accidentally push weird branches conflicting on all the files.

show more ...

Fix PR description HTML escaping, the surrounding `<pre>` tag shouldn't be escaped (#66322)

github-automation: Use a single comment for team mentions on pull requests (#66037)

This will reduce the number of notifications created when a pull request
label is added. Each team will only get

github-automation: Use a single comment for team mentions on pull requests (#66037)

This will reduce the number of notifications created when a pull request
label is added. Each team will only get a notification when their team's
label is added and not when other teams' labels are added.

show more ...

workflows/pr-subscriber: Handle libc++ and libc++abi labels (#66029)

Include the issue description in the subscription comment so that email notification is self-contained (#65839)

This makes it so that we don't need to open the issue to have the
description in our

Include the issue description in the subscription comment so that email notification is self-contained (#65839)

This makes it so that we don't need to open the issue to have the
description in our inbox on subscription.

show more ...

Improve the pull-request subcription notification format by adding the description and files statistics (#65828)

workflows: Add a simple pull request subscription workflow (#64913)

This new workflow will make it possible for people to subscribe to pull
requests based on the labels that are added. Labels will

workflows: Add a simple pull request subscription workflow (#64913)

This new workflow will make it possible for people to subscribe to pull
requests based on the labels that are added. Labels will be added
automatically to the pull requests based on the modified files and each
label will be associated with a GitHub team that will be notified when
the label is added.

See
https://discourse.llvm.org/t/changes-to-pull-request-subscription-system/73296

show more ...

[llvm][github] Allow github links in /cherry-pick actions

Differential Revision: https://reviews.llvm.org/D151191

[NFC][Py Reformat] Reformat python files in llvm

This is the first commit in a series that will reformat
all the python files in the LLVM repository.

Reformatting is done with `black`.

See more in

[NFC][Py Reformat] Reformat python files in llvm

This is the first commit in a series that will reformat
all the python files in the LLVM repository.

Reformatting is done with `black`.

See more information here:

https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Reviewed By: jhenderson, JDevlieghere, MatzeB

Differential Revision: https://reviews.llvm.org/D150545

show more ...

[clang][github] Try to fix multi-line py comment

Introduced in 09effa706a026c7ebcc01bf14f9f710cb1a8fa87

[llvm][github] Add good-first-issue comment to issues

Differential Revision: https://reviews.llvm.org/D146819

[github] Fix minor lint warnings (NFC)

Differential Revision: https://reviews.llvm.org/D135532

[llvm] Fix comment typos (NFC)

workflows: Release Workflow - Avoid selecting random reviewers when no phab review

If you pass a NULL reivew ID to the differential.revision.search API,
it returns all revisions and we were just tak

workflows: Release Workflow - Avoid selecting random reviewers when no phab review

If you pass a NULL reivew ID to the differential.revision.search API,
it returns all revisions and we were just taking the first one and
assuming it was associated with the commit in the PR.

We need to exit early if we can't find a Phabricator review associated
with a commit.

show more ...

workflows: Fix error when searching for backport reviewers

workflows: Fix pull request creation for backports

This was broken by 17d4796cc84618e9b15f9484e5576127c431bc60.

github: Automatically assign reviewers for backport requests

When there is a backport request, the GitHub Action that handles the
backport will now automatically assign the issue to the user(s) who

github: Automatically assign reviewers for backport requests

When there is a backport request, the GitHub Action that handles the
backport will now automatically assign the issue to the user(s) who
approved the commit in Phabricator and create an issue comment asking
them to review the request.

Reviewed By: thieta, kwk

Differential Revision: https://reviews.llvm.org/D126423

show more ...

github: Fix release automation /branch command with new repo

We started using the llvm/llvm-project-release-prs repo for
backport pull requests, but since this repo is not a fork of
llvm/llvm-projec

github: Fix release automation /branch command with new repo

We started using the llvm/llvm-project-release-prs repo for
backport pull requests, but since this repo is not a fork of
llvm/llvm-project it will reject pull requests from other repos. In
order to fix this, when ever someone uses the /branch command to request
a branch be merged into the release branch, we first copy the branch to
the llvm-project-release-prs repo and then create the pull request.

Reviewed By: thieta

Differential Revision: https://reviews.llvm.org/D126940

show more ...

github: Add a helpful message for issues without milestones

The /branch and /cherry-pick commands only work when an isssue has
a milestone, so give the user a helpful error message when they
try the

github: Add a helpful message for issues without milestones

The /branch and /cherry-pick commands only work when an isssue has
a milestone, so give the user a helpful error message when they
try these commands on issue without a milestone.

Reviewed By: thieta, kwk

Differential Revision: https://reviews.llvm.org/D125744

show more ...

[NFC][workflow] Fix issue where the workflow would say all PR's already exists

[workflow] Don't fail workflow if we already have a PR for an issue

When running /cherry-pick several times you will get an
error when it tries to create a new PR since there already
is one.

This c

[workflow] Don't fail workflow if we already have a PR for an issue

When running /cherry-pick several times you will get an
error when it tries to create a new PR since there already
is one.

This checks if we have PR first.

Fixes #54862

Reviewed By: tstellar

Differential Revision: https://reviews.llvm.org/D123657

show more ...

github: Switch release PR repository to llvm/llvm-project-release-prs

As discussed in https://discourse.llvm.org/t/creating-a-new-repository-for-release-branch-pull-requests/61339

Reviewed By: asl

github: Switch release PR repository to llvm/llvm-project-release-prs

As discussed in https://discourse.llvm.org/t/creating-a-new-repository-for-release-branch-pull-requests/61339

Reviewed By: asl

Differential Revision: https://reviews.llvm.org/D125851

show more ...

workflow: When updating the issueXX branch, use force push

Otherwise if you try to update the branch with a new /cherry-pick
from the same issue you will run into problems similar as to the
one show

workflow: When updating the issueXX branch, use force push

Otherwise if you try to update the branch with a new /cherry-pick
from the same issue you will run into problems similar as to the
one shown in this workflow:
https://github.com/llvm/llvm-project/runs/5864672298?check_suite_focus=true

Reviewed By: tstellar

Differential Revision: https://reviews.llvm.org/D123365

show more ...

Release Workflow: Remove cherry-pick-failed label when pull request is created

Reviewed By: nikic

Differential Revision: https://reviews.llvm.org/D121032

github: Add actions to automate part of the release workflow

This adds support for automatically cherry-picking and testing fixes for the
release branch using 'commands' in issue comments. The two

github: Add actions to automate part of the release workflow

This adds support for automatically cherry-picking and testing fixes for the
release branch using 'commands' in issue comments. The two supported commands are:

/cherry-pick <commit1> <commit2> ...

Which will backport and test commits from main. And also

/branch owner/repo/branch

Which will test commits from the given branch.

Reviewed By: alexbatashev, kwk

Differential Revision: https://reviews.llvm.org/D117386

show more ...