Steps to reproduce the bug:
- Create a branch locally (say patch1) and add
.deepsource.toml
- Push the changes to the repo
- Start deepsource analysis. It is now obvious that deepsource will look for the default branch (say master) for the initial analysis and hence will report with “Analysis Halted” tag
- Update the branch name from master to patch1 in settings
- deepsource analysis automatically begins as soon as it looks for
.deepsource.toml
file in patch1 - Results are flashed, however, the dashboard still shows “Analysis Halted” tag