[Github][CI] Rename New Premerge Jobs #138024
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch renames the new premerge job as suggested in https://discourse.llvm.org/t/github-ci-notifications-and-main-branch/85868/10. This uses more industry standard terms (like CI vs premerge checks which might be somewhat of a LLVM CI idiom?) and makes it more generic if we end up doing postcommit testing through Github.
|
@llvm/pr-subscribers-github-workflow Author: Aiden Grossman (boomanaiden154) ChangesThis patch renames the new premerge job as suggested in https://discourse.llvm.org/t/github-ci-notifications-and-main-branch/85868/10. This uses more industry standard terms (like CI vs premerge checks which might be somewhat of a LLVM CI idiom?) and makes it more generic if we end up doing postcommit testing through Github. Full diff: https://github.com/llvm/llvm-project/pull/138024.diff 2 Files Affected:
diff --git a/.ci/metrics/metrics.py b/.ci/metrics/metrics.py
index a5ee893650d63..5c53ebf6ade02 100644
--- a/.ci/metrics/metrics.py
+++ b/.ci/metrics/metrics.py
@@ -29,8 +29,8 @@
# name.
GITHUB_JOB_TO_TRACK = {
"github_llvm_premerge_checks": {
- "Linux Premerge Checks (Test Only - Please Ignore Results)": "premerge_linux",
- "Windows Premerge Checks (Test Only - Please Ignore Results)": "premerge_windows",
+ "Build and Test Linux (Test Only - Please Ignore Results)": "premerge_linux",
+ "Build and Test Windows (Test Only - Please Ignore Results)": "premerge_windows",
}
}
diff --git a/.github/workflows/premerge.yaml b/.github/workflows/premerge.yaml
index c315ee37646d2..5defe92debd6b 100644
--- a/.github/workflows/premerge.yaml
+++ b/.github/workflows/premerge.yaml
@@ -1,4 +1,4 @@
-name: LLVM Premerge Checks
+name: LLVM CI Checks
permissions:
contents: read
@@ -25,7 +25,7 @@ concurrency:
jobs:
premerge-checks-linux:
- name: Linux Premerge Checks (Test Only - Please Ignore Results)
+ name: Build and Test Linux (Test Only - Please Ignore Results)
if: >-
github.repository_owner == 'llvm' &&
(github.event_name != 'pull_request' || github.event.action != 'closed')
@@ -74,7 +74,7 @@ jobs:
include-hidden-files: 'true'
premerge-checks-windows:
- name: Windows Premerge Checks (Test Only - Please Ignore Results)
+ name: Build and Test Windows (Test Only - Please Ignore Results)
if: >-
github.repository_owner == 'llvm' &&
(github.event_name != 'pull_request' || github.event.action != 'closed')
|
joker-eph
reviewed
Apr 30, 2025
joker-eph
approved these changes
May 1, 2025
IanWood1
pushed a commit
to IanWood1/llvm-project
that referenced
this pull request
May 6, 2025
This patch renames the new premerge job as suggested in https://discourse.llvm.org/t/github-ci-notifications-and-main-branch/85868/10. This uses more industry standard terms (like CI vs premerge checks which might be somewhat of a LLVM CI idiom?) and makes it more generic if we end up doing postcommit testing through Github.
IanWood1
pushed a commit
to IanWood1/llvm-project
that referenced
this pull request
May 6, 2025
This patch renames the new premerge job as suggested in https://discourse.llvm.org/t/github-ci-notifications-and-main-branch/85868/10. This uses more industry standard terms (like CI vs premerge checks which might be somewhat of a LLVM CI idiom?) and makes it more generic if we end up doing postcommit testing through Github.
IanWood1
pushed a commit
to IanWood1/llvm-project
that referenced
this pull request
May 6, 2025
This patch renames the new premerge job as suggested in https://discourse.llvm.org/t/github-ci-notifications-and-main-branch/85868/10. This uses more industry standard terms (like CI vs premerge checks which might be somewhat of a LLVM CI idiom?) and makes it more generic if we end up doing postcommit testing through Github.
GeorgeARM
pushed a commit
to GeorgeARM/llvm-project
that referenced
this pull request
May 7, 2025
This patch renames the new premerge job as suggested in https://discourse.llvm.org/t/github-ci-notifications-and-main-branch/85868/10. This uses more industry standard terms (like CI vs premerge checks which might be somewhat of a LLVM CI idiom?) and makes it more generic if we end up doing postcommit testing through Github.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch renames the new premerge job as suggested in https://discourse.llvm.org/t/github-ci-notifications-and-main-branch/85868/10. This uses more industry standard terms (like CI vs premerge checks which might be somewhat of a LLVM CI idiom?) and makes it more generic if we end up doing postcommit testing through Github.