cloudfoundry / cloudfoundry/bosh
Stale branches to be delted
Open
@rkoster is already working on this.
Since Jul 2, 2026.
- Dominant language
- Ruby
- Stars
- 2.1k
- Forks
- 662
- Avg merge
- 5h 25m
- Merged PRs (30d)
- 2
Description
The following branches are years old and appear to be related to feature implementation. Many of the contributors to these branches are no longer active in the community.
I have prefixed a bunch of suspected dead branches with TO_DELETE-, list below. I propose these be deleted from github:
remotes/origin/TO_DELETE-264.x-cert-chaining
remotes/origin/TO_DELETE-acceptance-env
remotes/origin/TO_DELETE-application-cert-rotation
remotes/origin/TO_DELETE-bosh-cred-info
remotes/origin/TO_DELETE-create-swap-delete-fails-to-update-link-consumer-addresses
remotes/origin/TO_DELETE-create-vm-metadata
remotes/origin/TO_DELETE-deployments_without_configs
remotes/origin/TO_DELETE-diff-configs
remotes/origin/TO_DELETE-disk-usage
remotes/origin/TO_DELETE-fix-diff-local-addons
remotes/origin/TO_DELETE-hm-uses-exclude-parameters
remotes/origin/TO_DELETE-instance-vm-caching
remotes/origin/TO_DELETE-ipv6-ambiguity
remotes/origin/TO_DELETE-ipv6_dec29
remotes/origin/TO_DELETE-ipv6_feb2
remotes/origin/TO_DELETE-links-error-cleanup
remotes/origin/TO_DELETE-make-configs-backwards-compatible
remotes/origin/TO_DELETE-multi-cpi-backwards-compatibility
remotes/origin/TO_DELETE-nats-monitoring-enablement
remotes/origin/TO_DELETE-prototype-hotswap-multiple-options
remotes/origin/TO_DELETE-remove-instance-variables
remotes/origin/TO_DELETE-render-variable-0-instance
remotes/origin/TO_DELETE-ruby_sequel
remotes/origin/TO_DELETE-scratch-refactor-update-deployment
remotes/origin/TO_DELETE-specify-compiled-release
remotes/origin/TO_DELETE-task-paths
remotes/origin/TO_DELETE-tmp-utf8
remotes/origin/TO_DELETE-variable-provider
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.