feat(perforce): Implement stacktrace linking and file blame (annotate) logic #103636
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
Scope: Backend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
cathteng
approved these changes
Nov 19, 2025
mujacica
force-pushed
the
feat/perforce-backend-repo
branch
from
eef7490 to
1797637
Compare
mujacica
force-pushed
the
feat/perforce-backend-stack
branch
from
e2f403d to
2291a4b
Compare
mujacica
force-pushed
the
feat/perforce-backend-repo
branch
from
a8b00f2 to
04ad0d6
Compare
mujacica
force-pushed
the
feat/perforce-backend-stack
branch
from
1b702fd to
2f2e447
Compare
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
mujacica
force-pushed
the
feat/perforce-backend-repo
branch
from
b1f5dd9 to
4066443
Compare
This commit adds backend support for Perforce version control integration: - New Perforce integration with P4 client support - Repository and code mapping functionality - Stacktrace linking for Perforce depot paths - Tests for integration, code mapping, and stacktrace linking - Updated dependencies in pyproject.toml The integration supports: - Authentication via P4PORT, P4USER, P4PASSWD - Code mapping between depot paths and project structure - Source URL generation for stacktrace frames - Integration with Sentry's repository and code mapping systems
This commit adds backend support for Perforce version control integration: - New Perforce integration with P4 client support - Repository and code mapping functionality - Stacktrace linking for Perforce depot paths - Tests for integration, code mapping, and stacktrace linking - Updated dependencies in pyproject.toml The integration supports: - Authentication via P4PORT, P4USER, P4PASSWD - Code mapping between depot paths and project structure - Source URL generation for stacktrace frames - Integration with Sentry's repository and code mapping systems
mujacica
force-pushed
the
feat/perforce-backend-stack
branch
from
cd473f2 to
91415ca
Compare
ryan953
pushed a commit
that referenced
this pull request
Dec 9, 2025
…) logic (#103636) This commit adds backend support for Perforce version control integration: - Stacktrace linking for Perforce depot paths - Tests for integration, code mapping, and stacktrace linking
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds backend support for Perforce version control integration:
Requires: #103287, #103171, #103635