example: https://archive.softwareheritage.org/swh:1:cnt:a6463d2ce390990c31c2f2fa8019606721f0ca13;origin=http://git.savannah.gnu.org/git/gnugo.git/

Thanks @anlambert for the detailed explanation.
This is exactly right !

Hi @sdruskat,
Thanks for your input.
I agree with you that for the end user this looks like a problem.
On the other hand, we are an infrastructure that needs to consider many platforms for the long term, so we can't pick and choose whatever feels more comfortable for the user.

@vlorentz I'm not sure it is an easy hack, could you review the task and decide?

@anlambert: Can you also update this page as well- https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html
Adding the first item (hal-02446202) to the references?

publiccode.yml : https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html

@anlambert thanks!
I'll do the translation so I'm claiming the task.

@anlambert: great. Thanks !

https://github.com/fnielsen/scholia

@vlorentz : If you can check the Slug in the deposit DB of this artifact, it might be je-suis-gpl
And do the deposit with the same Slug for linking purposes.

The deposit is visible and accessible on HAL without a link to SWH (because we rejected it).

1. this ticket is open on HAL side as well, but I don't know at what priority level.
2. we do check and than we reject it (this is why there is no link)
3. I tagged it with [HAL] because I assume we want to keep the rejection but we need to make sure it is fixed

I can change the title to Make sure this is fixed

This might be resolved with T2149 ?

Opened this issue to inform Dirk Roorda:
https://github.com/annotation/text-fabric/issues/54

Looks good to me too :-)

Oh I see..
I was just referencing the documentation and I saw that and it seemed like an error.
But I remember now we already had this discussion.
I would show the same page as without the /1, if possible...
In any case a 404, looks like an error..

@vlorentz I'm not convinced about having the url in the text of the badge.
I understand that a fork can use the "wrong" badge, by using the main repository's badge.
But the sha1 is already very long for a badge and this is really kind of a gimmick link :-)

Thanks for the images at the beginning of the diff, the badges are very cool !
I pinged @marla.dasilva to see the result and we might want to change the colors to more positive colors.
We are planning to meet about that on Friday, maybe we can even show it to @rdicosmo :-)

I don't feel comfortable to accept revisions, globally... but your diff looks solid.