When developing our software, we use the common approach of working in a ‘development’ branch, and merging that branch into master once we push for a new release.
We usually merge into master with a ‘fast-forward’ approach, so no new ‘merge’ commit gets created.
However, this creates issues for codecov.
When looking at our CI pipeline, the codecov part says: “remained the same compared to hash-of-commit”.
On the codecov website, the master branch does not get updated either, resulting in a wrong coverage badge…
This is really frustrating, as I do not want to create merge requests etc. for the sole purpose of getting codecov to work! I feel codecov should see that the master branch pointer has moved and use the correct report.