• 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>...]

Dod -

• Client id/org id/ name/ some info to map run to client
• Storage of said info with schema/db design
• Mapping of said info in website

Add unencrypted info somewhere in postgres separately

When a new release is created only the third subversion is incremented so the third sub-version can never be 0.

Dod -

• Schema/db design for keeping data for now
• pipelines to sync/run jobs

After fix -

• Update github action url
• Alokit-Innovations/devprofiler-cloudrun#82

Alongwith better metrics for churn, design and record metrics to identify repo/code specific features

Dod -

• All pipes/actions etc get devprofiler from a consistent url
• Change name if need be
• automatic versioning using Semver or similar alternative

PR review template to be added to org as well as specific instructions for repos -
PR for dev-profiler