openzim / freecodecamp

FreeCodeCamp.org scraper (to ZIM)
GNU General Public License v3.0
4 stars 2 forks source link

Zimfarm readyness #14

Closed benoit74 closed 1 year ago

benoit74 commented 1 year ago

Fix #11 Fix #13

Changes : MANY (sorry)

Some details:

I suggest that we release this as a 1.0.0 since it has not yet been released anyway.

NOTA: we have to enable Trusted Publishing for this repo.

benoit74 commented 1 year ago

Is there any way to tell CodeFactor to ignore a check on a specific line (like I did for Ruff on the specific line which raised an issue)?

rgaudin commented 1 year ago

Is there any way to tell CodeFactor to ignore a check on a specific line (like I did for Ruff on the specific line which raised an issue)?

Codefactor itself no but codefactor is just an integrated set of open tools (with private config). In this case it's a Bandit rule raising so silence it as such

kelson42 commented 1 year ago

Is there any way to tell CodeFactor to ignore a check on a specific line (like I did for Ruff on the specific line which raised an issue)?

Yes AFAIK with codefactor web ui

benoit74 commented 1 year ago

Is there any way to tell CodeFactor to ignore a check on a specific line (like I did for Ruff on the specific line which raised an issue)?

Yes AFAIK with codefactor web ui

Looks like I do not have proper access rights ... anyway, done through inline comment ok

rgaudin commented 1 year ago

Is there any way to tell CodeFactor to ignore a check on a specific line (like I did for Ruff on the specific line which raised an issue)?

Yes AFAIK with codefactor web ui

We obviously don't want to set exceptions on Codefactor UI!

rgaudin commented 1 year ago

Looks like I do not have proper access rights ... anyway, done through inline comment ok

You're admin on this repo.

benoit74 commented 1 year ago

Sorry about the files that are considered by git as "deleted/new" instead of been "moved", unfortunately there is little I can do on this.

Should I list in the first comment all files that are considered as "deleted/new" which have indeed only been "moved", so you can git diff them manually?

I agree this is a real pain.

For instance here:

rgaudin commented 1 year ago

Should I list in the first comment all files that are considered as "deleted/new" which have indeed only been "moved", so you can git diff them manually?

I guess. We can try next time