Cleaning up stale branches

[JP-Ellis]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Description

I would like to clean up the old branches in this repository. Specifically, I am considering pruning the following branches:

Branch	Updated	Un-merged commits
travis-stages	6 years ago	9
setup-releases	6 years ago	18
stateless-contracts	6 years ago	1
always-run-e2e	6 years ago	1
docs/verifier_docs_examples	3 years ago	6
feat/V31	2 years ago	12
docs/kafka_example	2 years ago	3
feat/ffi-consumer1	2 years ago	2
snyk-fix-e0893507f8bdf5341d8ffe2cfae4bd0f	2 years ago	1
feat/ffi-provider1	2 years ago	8
pact_publish_instructions	last year	1
repro/issue-310	last year	1

¹Will be kept until v3 is released.

I will leave this issue open for a month to gather feedback before I do anything drastic.

Has this been requested on Canny?

No response

Motivation

Some of these branches have not been touched in years and therefore are unlikely to provide much value anymore. Especially with the overhaul required to v3 and the switch to the Pact Rust core, many changes will be either redundant or very difficult to apply in the new codebase.

Have you tried building it?

No response

Self-service

• I'd be willing to contribute this feature to Pact Python myself.

[JP-Ellis]

I have recently gone over all the stale branches above, and prefixed them which archived/. The idea is to break the workflow of anyone still using them. If no one notices that the branch has been renamed, then it should be safe to delete them.

I will give another few months before deleted the archived branches.