Extract VCSDriver independent interface
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
In the long run it would be nice to be able to choose whether to use Mercurial or Git as VCS backend.
As a first step we should refactor things so that we have a VCSDriver independent interface with a method to select which driver to use. Currently we have e.g. HgRepository class which has several static methods.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading the existing HgRepository class and its static methods to understand the current VCS coupling. Identify the project entry points that use those methods and determine how a driver-selection method would fit. Done means the VCSDriver interface and driver selection are independent of the Mercurial implementation, with existing behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100