When modifying the default branch of a project, consider if/how to handle migrating the default tracking context as well for better UX
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
In some instances, it may be surprising for users who modify their default branch and then find that vulnerability tracking is no longer enabled on the default branch because it did not migrate with their default branch.
Additionally, during Iteration 1, it is necessary for us to make default tracking follow the default branch until all historical data is appropriately attributed lest any data become orphaned.
But after this, it becomes a question of whether or not tracking should follow the default branch around or not? Should we warn users that the new default branch will not be tracked by default? What if the new default branch has vulnerability history? We need to consider how we expect this work