Description We have several issues with codecov trying to guess the base commit to compare against, so we decided to use the -N flag to tell it ourselves. I’ve seen several other people having the base report problem ( one , two , three ). All suggestions to fix this are using the -N flag… but we canno…

Hey y’all, just clarifying a couple things for this thread and all future readers. [image] 1.) We have a feature to manually pick parents of commits (docs) 2.) We do not have a feature to manually pick base of a PR. 3.) Codecov will always pick the base of the PR as where the branch happened (o…

Flag -N to set the base report does not work

Support Bug Fixes

scott February 14, 2020, 10:28pm 5

I also need this functionality and added it to the feature request section. Set base commit

2 Likes

Topic		Replies	Views
Comparing report to a wrong commit causes "No report found to compare against" error Support github	4	1230	February 6, 2020
CodeCov showing impossible drops in coverage	2	526	February 5, 2020
Set base commit Feature Requests	14	2912	February 16, 2021
Unable to determine a parent commit to compare against in base branch after Squash and Merge Support	20	1949	April 8, 2021
Codecov picks up incorrect base commit from feature branch instead from base branch for Github PRs	1	412	March 4, 2020

Flag -N to set the base report does not work

Related topics