README src/calculateRank.js Link Inconsistent

[conorvenus]

Describe the bug

The src/calculateRank.js link inside the README file does not work consistently, i.e., if you are on https://github.com/anuraghazra/github-readme-stats and you click it, it takes you to https://github.com/anuraghazra/src/calculateRank.js incorrectly.

Expected behavior

I would expect to be taken to the src/calculateRank.js file within the current repository.

Screenshots / Live demo link

https://streamable.com/ocjjn1

Additional context

No response

[rickstaa]

Thanks for the bug report. This will be fixed when #3067 is merged 👍🏻.

[a-s-t-e-y-a]

@rickstaa I solved the readme.md issue by fixing the link to https://github.com/anuraghazra/github-readme-stats/blob/master/src/calculateRank.js

[rickstaa]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

[qwerty541]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

Nice, let's wait for their response.

[rickstaa]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

Nice, let's wait for their response.

I just got several responses:

It looks like a bug in their system, which they are trying to solve👍🏻.

[qwerty541]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

Nice, let's wait for their response.

I just got several responses:

It looks like a bug in their system, which they are trying to solve👍🏻.

@rickstaa Should we use absolute path until this bug will be fixed in your opinion? It can take some weeks or months untils patched version will be deployed on production.

[rickstaa]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

Nice, let's wait for their response.

I just got several responses:


It looks like a bug in their system, which they are trying to solve👍🏻.

@rickstaa Should we use absolute path until this bug will be fixed in your opinion? It can take some weeks or months untils patched version will be deployed on production.

I'm okay with merging a pull request that uses the absolute path, keeping this issue open, and reverting it later when the problem is fixed on GitHub's side 👍🏻.

[qwerty541]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

Nice, let's wait for their response.

I just got several responses:


It looks like a bug in their system, which they are trying to solve👍🏻.

@rickstaa Should we use absolute path until this bug will be fixed in your opinion? It can take some weeks or months untils patched version will be deployed on production.

I'm okay with merging a pull request that uses the absolute path, keeping this issue open, and reverting it later when the problem is fixed on GitHub's side 👍🏻.

I have opened a pull request with temporary solution for both src/calculateRank.js and vercel.json files. Please check it #3389

[rickstaa]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

Nice, let's wait for their response.

I just got several responses:


It looks like a bug in their system, which they are trying to solve👍🏻.

@rickstaa Should we use absolute path until this bug will be fixed in your opinion? It can take some weeks or months untils patched version will be deployed on production.

I'm okay with merging a pull request that uses the absolute path, keeping this issue open, and reverting it later when the problem is fixed on GitHub's side 👍🏻.

I have opened a pull request with temporary solution for both src/calculateRank.js and vercel.json files. Please check it #3389

Great, let's keep this issue open as a reference! I will inform you when GitHub emails me that the bug is fixed 👍🏻.

[qwerty541]

Looks like there is a bug on GitHub's side. I just opened a ticket with the support.

Originally posted in #3140.

Nice, let's wait for their response.

I just got several responses:


It looks like a bug in their system, which they are trying to solve👍🏻.

@rickstaa Should we use absolute path until this bug will be fixed in your opinion? It can take some weeks or months untils patched version will be deployed on production.

I'm okay with merging a pull request that uses the absolute path, keeping this issue open, and reverting it later when the problem is fixed on GitHub's side 👍🏻.

I have opened a pull request with temporary solution for both src/calculateRank.js and vercel.json files. Please check it #3389

Great, let's keep this issue open as a reference! I will inform you when GitHub emails me that the bug is fixed 👍🏻.

Thanks!