Describe the bug
The Le Git Graph commit graph page shows commit status checkmarks, Even when the commit status should indicate failed or absent. When clicking on the checkmark for these commits, it does display correctly that the checks have failed.
To Reproduce
Steps to reproduce the behavior:
Go to a repo (a private repo in my case, using fine grained personal access tokens with metadata, content and commit status permissions)
Click on the 'Commits' tab
Look to the right of the commit date
See the wrong commit status
Expected behavior
I expect commits with failed checks to show an ❌ and commits without any checks to not show a ❌ or ✔ at all
Screenshots
Le Git Graph commit graph page with wrong status:
And:
Commit page with correct commit status:
Version information:
OS: Windows 10
Browser: Firefox 116.0.3
Version: 1.2.0
A private repo
Additional context
As said above, I was using a new fine grained personal access token with metadata, content and commit status permissions with read-only access. I don't know if this has anything to do with the bug, but I'm mentioning this here just to be sure
Describe the bug The Le Git Graph commit graph page shows commit status checkmarks, Even when the commit status should indicate failed or absent. When clicking on the checkmark for these commits, it does display correctly that the checks have failed.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect commits with failed checks to show an ❌ and commits without any checks to not show a ❌ or ✔ at all
Screenshots Le Git Graph commit graph page with wrong status:
And:
![afbeelding](https://github.com/NirmalScaria/le-git-graph/assets/5381337/49531309-2875-44d3-8bae-50ad4c79c8e3)
Commit page with correct commit status:![afbeelding](https://github.com/NirmalScaria/le-git-graph/assets/5381337/087fbb6d-8b8e-4a68-81b5-f1cee68a0220)
Version information:
Additional context As said above, I was using a new fine grained personal access token with metadata, content and commit status permissions with read-only access. I don't know if this has anything to do with the bug, but I'm mentioning this here just to be sure