Adding forked tP to CodeCov💡

[bryanwee023]

Hi guys,

If you guys are a confused on the instructions to add your organisation's fork to CodeCov:

1. Sign up to CodeCov
2. Enable Github Actions on your fork
3. Make a trivial commit to your fork (This runs the CI/CD workflow which uploads a report to CodeCov)
4. CodeCov should have detected your fork!

I took a embarrassing amount of time figuring this out. So hopefully this useful to some of you :)

[damithc]

@bryanwee023 this didn't help? Or was some info missing in relevant part of the DevOps Guide?

[bryanwee023]

@damithc oh, the phrasing must have thrown me off.

Perhaps it will be better to merge the last 2 sentences?

That will enable the Github Actions that are already included in the repo you forked set up codecov, as explained in the DevOps guide

I interpreted the last sentence as a standalone step 😅 .

[vimuthm]

Haha I too spent an unexpected amount of time on this xD.

To add on :

• When you authorize third party access to CodeCov from github, ensure the newly created organization is ticked, because it might not be so by default
• The trivial commit @bryanwee023 mentioned can be where you update index.md with the new badge. (I got stuck here because I was expecting the repo to be recognized by CodeCov before committing, so I went down a rabbithole of links provided by CodeCov on setting up repos with Gradle)

[damithc]

I interpreted the last sentence as a standalone step 😅 .

It is a separate step. I don't think enabling GitHub Actions automatically sets up CodeCov. But setting up CodeCov before enabling GitHub actions might work better. And yes, it's best to mention that CodeCov report will only trigger the next time something is pushed to the repo. Will tweak the instructions next time (too late to do that for this round though, as most have forked already).