Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix path not in the working tree bug in bitbucket flow #44

Open
MuskanPaliwal opened this issue May 29, 2023 · 0 comments
Open

Fix path not in the working tree bug in bitbucket flow #44

MuskanPaliwal opened this issue May 29, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@MuskanPaliwal
Copy link
Member

  • When the dev-profiler runs on the bitbucket repos, somehow it doesn't get the whole commit history of the repo and hence, it is not able to get the hunk-info of a pr_head commit.
  • We don't face the same problem in github because we have made the fetch-depth argument 0 so it takes all the history and find hunk_info and right now, we don't have any way to provide the current barnch path to the dev-profiler in bitbucket.
  • So decided to skip it as of now.
  • The error message that git diff command gives in pipeline run: error: "fatal: ambiguous argument '99e106b31a9b': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]
@MuskanPaliwal MuskanPaliwal added the bug Something isn't working label May 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants