hound-search/hound

feature request: perforce support

Open

#179 opened on Dec 14, 2015

View on GitHub
 (1 comment) (4 reactions) (0 assignees)JavaScript (5,470 stars) (606 forks)batch import
enhancementhelp wanted

Description

We use perforce where I work, I've had mixed success trying to use it via git-p4. Could hound be extended to support p4?

Contributor guide

Tech stack
javascript
Domain
backendtoolingsearch
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
understanding of hound's existing VCS integrationsfamiliarity with Perforce CLI or API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Start by examining the repository's current VCS integration, likely in the lib/ directory, to understand how git support is implemented. Then design a similar adapter for Perforce. Check if any prior attempts or discussions exist in the issue's single comment (if available) or in the repository's wiki. Since the issue is from 2015, also assess the project's current activity and maintainer responsiveness before investing significant effort.
feature request: perforce support · hound-search/hound#179 | Good First Issue