Disable comment trigger for Performance and Load Tests

[magicgoody]

Reference PR https://github.com/apache/beam/pull/28915/files issue_comment removed

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[andreydevyatkin]

@Abacn Shall we disable comment trigger for Perf and Load tests only or for all workflows? Not sure if we actually need to disable it, but I see you started doing it here: #28915

[Abacn]

@Abacn Shall we disable comment trigger for Perf and Load tests only or for all workflows? Not sure if we actually need to disable it, but I see you started doing it here: #28915

Yes, for Perf and Load tests (and postcommits that have Jenkins counterpart). Until we replaced the comment trigger the precommit issue_comment triggered are kept because PR testing are most likely need them, and the number of precommit is tolerable for the queueing issue described in #28909

[Abacn]

Notice that the tests that this PR involves are mostly newly added workflows after #28915

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @damccorm for label build.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[magicgoody]

@Abacn Shall we disable comment trigger for Perf and Load tests only or for all workflows? Not sure if we actually need to disable it, but I see you started doing it here: #28915

Yes, for Perf and Load tests (and postcommits that have Jenkins counterpart). Until we replaced the comment trigger the precommit issue_comment triggered are kept because PR testing are most likely need them, and the number of precommit is tolerable for the queueing issue described in #28909

Hello, thanks for checking
I also removed such workflow trigger for 4 PostCommit jobs where part of Jenkins is not yet disabled.