pierrejeambrun opened a new pull request, #74039:
URL: https://github.com/apache/airflow/pull/74039

   Selecting a run that carried a config turned the whole **Trigger** button 
into a dropdown menu, so every trigger from that view cost an extra click on 
the most common action (reported in #73177).
   
   This restores the one-click trigger as a GitHub-style split button: the main 
button always triggers in a single click, and re-using the selected run's 
config moves to a caret that appears **only** when the selected run actually 
carried a config. When no config run is selected, the button looks and behaves 
exactly as before.
   
   ### Screenshots
   
   | One-click trigger (no config run) | Split button (config run selected) | 
Config menu open |
   | --- | --- | --- |
   | _drag `trigger-normal.png` here_ | _drag `trigger-split.png` here_ | _drag 
`trigger-menu-open.png` here_ |
   
   closes: #73177
   related: #69820
   
   Independent implementation of the UX requested in the issue. It takes the 
same split-button direction as the draft in #73564, differing in that the main 
action stays a single click and the caret is shown only when the selected run 
carried a config (no redundant "trigger with config" entry), and it keeps the 
required `dagId` prop on the modal.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to