[
https://issues.apache.org/jira/browse/CAMEL-23932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100697#comment-18100697
]
Guillaume Nodet commented on CAMEL-23932:
-----------------------------------------
This issue is being investigated by a coding agent (Claude Code on behalf of
gnodet).
Analysis: The existing branch cleanup workflow (pr-cleanup-branches.yml) only
covers automated/upgrade* branches. Expanding it to delete any non-protected
branch pushed to apache/camel when its PR is merged or closed (excluding
release branches like camel-*.x and main) would address the stale-branch
accumulation. 6 stale branches from merged/closed PRs confirmed on the repo.
_Note: This comment was generated by a coding agent and requires manual
verification._
> Ensure AI agents are respecting the Git branch recommendations to not fill up
> the apache repo with outdated branches
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-23932
> URL: https://issues.apache.org/jira/browse/CAMEL-23932
> Project: Camel
> Issue Type: Task
> Reporter: Aurélien Pupier
> Assignee: Guillaume Nodet
> Priority: Major
> Attachments: screenshot-1.png
>
>
> despite the agents.md containg:
> {noformat}
> - An agent should prefer to use his own fork to push branches instead of the
> main apache/camel repository. It avoids to fill the main repository with a
> long list of uncleaned branches.
> - An agent must provide a useful name for the git branch. It should contain
> the global topic and issue number if possible.
> - After a Pull Request is merged or rejected, the branch should be deleted.
> {noformat}
> there are a lot of branches created on Apache repo for no real reasons and
> which are not cleaned up after. It is causing all users and CI to lost time
> and disk space
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
