Weixin-Xu opened a new issue, #13402:
URL: https://github.com/apache/gluten/issues/13402

   ### Backend
   
   VL (Velox)
   
   ### Bug description
   
   GitHub labeling and issue templates do not properly support the Bolt backend.
   
   Actual behavior:
   1. A PR changing only `cpp/bolt/` receives VELOX because the labeler
      matches all files under `cpp/**/*`. No BOLT rule is configured.
   2. The Bug Report template requires a Backend selection but only offers
      VL (Velox) and CH (ClickHouse).
   3. The Build problem template asks users to describe how they built
      Velox, even when reporting a Bolt build issue.
   
   Expected behavior:
   - Bolt-specific changes receive BOLT.
   - Velox-specific changes receive VELOX.
   - Shared C++ changes and PRs touching both backends receive both labels.
   - The Bug Report template offers BOLT (Bolt).
   - The Build problem template asks which Gluten backend was being built.
   
   Steps to reproduce:
   1. Open a PR changing only a file under `cpp/bolt/` and inspect its labels
      after the PR Bot runs.
   2. Open the Bug Report form and inspect the Backend dropdown.
   3. Open the Build problem form and inspect the default problem description.
   
   This concerns GitHub configuration, not runtime behavior.
   VL is selected because the current form does not offer Bolt.
   
   This description was prepared with assistance from OpenAI Codex (GPT-6).
   
   ### Gluten version
   
   main branch
   
   ### Spark version
   
   None
   
   ### Spark configurations
   
   _No response_
   
   ### System information
   
   _No response_
   
   ### Relevant logs
   
   ```bash
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to