Ensure to keep previous test behavior after initializing expkw to 0

Looks good to me. There is a typo in commit message though, s/store_date/store_data/.

I think it would be better to avoid hardcoding test inputs and expected values in graphql responses.

You must keep SWHID in uppercase in docstrings (see documentation).

Looks good to me.

This has been implemented and deployed.

In T4254#85326, @bchauvet wrote:

Thanks for the investigation :)
I'll close the related issues

The remaining question is : should we consider all staff users as moderators or should we rely on the permission above only ?

Considering all staff members as moderators seems to make sense to me

See T4254#85310 for the cause of the issue.

See T4254#85310 for the cause of the issue.

The issue was due to the missing permission swh.web.add_forge_now.moderator for your user account on staging.
I just granted it to you so you should now be able to see the missing info.

Looks good to me.

Rebase

Looks good to me.

Looks good to me.

Thanks mypy !

Rebase

Update Bazaar loader status as it is now deployed to production.

This has been implemented and deployed.

Looks good, thanks ! You will have to rebase the diff before landing it.

It's fixed see details in T3862.

@anirudhlakhotia, sorry but you are wrong here, forge URLs are santized in the moderation dashboard. This is exactly the purpose of the use of the $.fn.dataTable.render.text() render function (see Security doc of datatables).

Use a table to enumerate available loaders instead of a grid (see updated diff description).

Use a table to enumerate available loaders instead of a grid (see updated diff description).