(texera) branch gh-readonly-queue/main/pr-7062-40caed3adb048b57a2a42556fccda128439881b6 created (now 42493c6d8e)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-merge-queue[bot] pushed a change to branch gh-readonly-queue/main/pr-7062-40caed3adb048b57a2a42556fccda128439881b6
in repository https://gitbox.apache.org/repos/asf/texera.git


      at 42493c6d8e ci: skip contributor template check for renovate-bot's User account (#7062)

This branch includes the following new commits:

     new 42493c6d8e ci: skip contributor template check for renovate-bot's User account (#7062)

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

(texera) 01/01: ci: skip contributor template check for renovate-bot's User account (#7062)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-7062-40caed3adb048b57a2a42556fccda128439881b6
in repository https://gitbox.apache.org/repos/asf/texera.git

commit 42493c6d8efa49d6dbef7121d1d78cf3d6036a7c
Author: Yicong Huang <17...@users.noreply.github.com>
AuthorDate: Wed Jul 29 19:22:41 2026 -0400

    ci: skip contributor template check for renovate-bot's User account (#7062)
    
    ### What changes were proposed in this PR?
    
    The `contributor-checks` job in
    `.github/workflows/contributor-checks.yml` gates on
    `github.event.sender.type != 'Bot'` so it won't nag automated PR/issue
    openers about not following the contribution template.
    
    That gate catches GitHub App bots (e.g. `dependabot[bot]`, whose account
    `type` is `Bot`) but **not** Renovate, which on this repo runs under a
    regular User account: `renovate-bot` has `type: User`, so it slips
    through and gets the "the description doesn't follow our template"
    warning on every dependency-update PR (example: #7060).
    
    This PR excludes `renovate-bot` explicitly by login:
    
    ```yaml
    if: >-
      github.event.sender.type != 'Bot' &&
      github.event.sender.login != 'renovate-bot'
    ```
    
    ### Any related issues, documentation, discussions?
    
    Closes #7063.
    
    Example of the false warning: #7060.
    
    ### How was this PR tested?
    
    - Confirmed via the GitHub API that `renovate-bot` has `type: User` (not
    `Bot`), which is why the existing `sender.type != 'Bot'` gate did not
    exclude it.
    - Validated the workflow YAML parses and the folded `if:` expression
    resolves to the intended single-line condition.
    - The change is confined to the job-level `if:` gate; no `run:` step or
    untrusted-input interpolation is touched.
    
    ### Was this PR authored or co-authored using generative AI tooling?
    
    Generated-by: Claude Code (Opus 4.8)
    
    Co-authored-by: Claude Opus 4.8 (1M context) <no...@anthropic.com>
---
 .github/workflows/contributor-checks.yml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/contributor-checks.yml b/.github/workflows/contributor-checks.yml
index 2f8592a4f8..e643859e03 100644
--- a/.github/workflows/contributor-checks.yml
+++ b/.github/workflows/contributor-checks.yml
@@ -51,7 +51,13 @@ permissions:
 
 jobs:
   contributor-checks:
-    if: github.event.sender.type != 'Bot'
+    # Skip automated PR/issue openers. GitHub App bots (e.g. dependabot)
+    # have sender.type == 'Bot', but Renovate runs under a regular User
+    # account (`renovate-bot`, type: User) and would otherwise be nagged
+    # for not following the template, so exclude it explicitly by login.
+    if: >-
+      github.event.sender.type != 'Bot' &&
+      github.event.sender.login != 'renovate-bot'
     runs-on: ubuntu-latest
     steps:
       # pull_request_target and issues both resolve to the trusted base