Skip to content

Proposal to Clean Up Remote Branches #84

@ilfreedom

Description

@ilfreedom

Description

We have accumulated multiple remote branches in the repository, many of which are no longer active or relevant to the current development workflow. To keep the repository clean and maintainable, I propose deleting the following remote branches:

Branches proposed for deletion:

TAMU-dev
anax-in-container
check-vulnerabilities
crop-insights-page
dashboard
dashboard-fields
dashboard-fields-landing-page
documentation/compo-doc
gaurav-new-updates
md-manage-sensor
ng-upgrade
on-the-edge
open-horizon-integration
settings-page/language-temperature
splash-page
watering-insights-page
wifi-ota-support

Branches to keep:

main (default branch)
development (active development)
ph-dev (active development)

Rationale

Many of the branches listed above appear to be outdated or have already been merged into main or development.
Keeping unused branches increases clutter and makes branch management more difficult.
A clean repository improves navigation and reduces potential confusion for contributors.

Next Steps

Feedback:
Please review the proposed list of branches to be deleted.
If you believe any of the listed branches should be retained, kindly comment on this issue and provide the reasons why it should be kept.

Action:
After collecting feedback and reaching a consensus, we will proceed to delete the agreed-upon branches using:
git push origin --delete <branch_name>

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions