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

   I wanted to clean up a lot of our buttons.
   
   The buttons with text in the header of each details card was getting too 
cumbersome, so they are all now just icons.
   
   Some icons like toggling groups or adjusting the logs page just didn't have 
the correct background colors.
   
   Use our new ButtonToggleGroup component in more place.
   
   Before:
   <img width="1864" height="594" alt="Screenshot 2026-01-14 at 4 26 56 PM" 
src="https://github.com/user-attachments/assets/a7ec3c7a-5c1a-4110-b9e6-814a37364f33";
 />
   
   After:
   <img width="1472" height="449" alt="Screenshot 2026-01-14 at 4 52 41 PM" 
src="https://github.com/user-attachments/assets/3dea35d6-0663-47f4-9147-81e9e8eac7a6";
 />
   
   
   
   ### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes (please specify the tool below)
   
   Cursor
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


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