Codecov Report

Merging #3277 (f35022e) into main (5034b84) will decrease coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3277      +/-   ##
==========================================
- Coverage   61.65%   61.51%   -0.14%     
==========================================
  Files         426      426              
  Lines       27399    27399              
==========================================
- Hits        16892    16855      -37     
- Misses       9506     9540      +34     
- Partials     1001     1004       +3     

see 10 files with indirect coverage changes

Flags with carried forward coverage won't be shown. Click here to find out more.

@AlekSi I realised now there in no clear way to find issue open or closed by issue url like we used in our test, is there any better way?

I think we could use the GitHub API via https://github.com/google/go-github. We have some examples there: https://github.com/FerretDB/github-actions/blob/main/conform-pr/main.go

@KrishnaSindhur, any news? Anything we could help you with?

Will raise a PR shortly!!

@AlekSi this PR is like draft just want to know how to test locally? github token is required to test it locally and some repo information please check!!

what we should do if we have below URL? should we ignore or catch it?
https://api.github.com/repos/owner/https://github.com/FerretDB/FerretDB/issues/2733

we have to remove // want

That would be the equivalent of removing a test, and we want to keep that test. Let's find some other solution. For example, we could remove // want … part if the file name is testdata.go.

Let's also gather all URLs first, remove duplicates, and then check them. Right now we check the same issue multiple times, quickly running over a rate limit for unauthenticated requests.

@AlekSi should i make change to remove? this should be check in todo statement to check file name something and then avoid // want ..

// want … part if the file name is testdata.go.

so then how do we check for duplicate issue without a api hit?

so then how do we check for duplicate issue without a api hit?

By collecting already checked URLs and not checking the same URL twice

Thank you for all the hard work!

hey sorry i was occupied with some other things could not spend time last 2 weeks
@AlekSi

No worries! :)