You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This will be a good spike / prototype to see what the real effort would be to add a Perforce specific concept into Sourcegraph. This assumes we are still converting depots to git and is intended to see what a minimal change would look like.
If it goes well, we may have something to ship for March.
This will hopefully help us discover many unknown unknowns and clarify the complexity of things we already know we need to do.
We should keep in mind that there is at least a 50% chance we'll stop converting to git and design our abstractions in a way that can easily accommodate this.
This will be a good spike / prototype to see what the real effort would be to add a Perforce specific concept into Sourcegraph. This assumes we are still converting depots to git and is intended to see what a minimal change would look like.
If it goes well, we may have something to ship for March.
This will hopefully help us discover many unknown unknowns and clarify the complexity of things we already know we need to do.
We should keep in mind that there is at least a 50% chance we'll stop converting to git and design our abstractions in a way that can easily accommodate this.
High level changes required
Links below will be to a test Perforce depot on the dogfood instance
with a url likemoving all URL changes to Perforce Change List Number Support in URLs #40330https://instance/owner/depot-name/-/change/1234p4-fusionandgit-p4, eg[p4-fusion: depot-paths = "//test-perms/": change = 83725][changelist id] -prefix in commit subjects