Subham-KRLX opened a new pull request, #61341:
URL: https://github.com/apache/airflow/pull/61341

   This PR adds a new breeze command `generate-issue-content-airflowctl` that 
generates issue content for testing airflowctl releases, similar to the 
existing `generate-issue-content-core` command.
   
   The command filters git log to only include commits that modified files in 
the `airflow-ctl/` directory, enabling targeted release testing of airflowctl 
components.
   
   **Changes made:**
   - Added `is_airflowctl` parameter to 
[get_git_log_command()](cci:1://file:///Users/subhamsangwan/airflow/dev/breeze/src/airflow_breeze/commands/release_management_commands.py:2710:0-2735:18)
 and 
[get_changes()](cci:1://file:///Users/subhamsangwan/airflow/dev/breeze/src/airflow_breeze/commands/release_management_commands.py:2766:0-2785:79)
 functions to support directory-specific filtering
   - Created new CLI command 
[generate_issue_content_airflowctl()](cci:1://file:///Users/subhamsangwan/airflow/dev/breeze/src/airflow_breeze/commands/release_management_commands.py:2949:0-2999:5)
 with same options as core command (--github-token, --previous-release, 
--current-release, --excluded-pr-list, --limit-pr-count)
   - Updated `RELEASE_AIRFLOW_CTL_COMMANDS` configuration to include the new 
command
   - Added parameter configuration in `RELEASE_MANAGEMENT_PARAMETERS` for 
proper command display
   
   **Testing performed:**
   - Verified command help displays correctly with all expected parameters
   - Confirmed git log filtering works properly for `airflow-ctl/` directory
   - Code passes ruff linting and formatting checks
   
   closes: #61323
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (Gemini-For pr description)
   


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