-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes for action failing with "Cannot read properties of undefined (reading 'split')" | Updated selectors & matches #76
Conversation
…tHub's page format
…ion-error-fixes 🐛 Adapted contributions stats extractor function to match with new Gi…
hey guy, i just tried building svg using your repo, but it still and the action in this |
Wow! That was quick. |
@SkyDynamic , will have a look now! Thanks |
@SkyDynamic , figured it out. Turns out one more file should have included the update. I'll add a new commit with a fix and let's see. |
@milaabl I don't konw is there no definition the also, I will provide the action line too, please click there |
Yes, I see that error, currently working on it |
@SkyDynamic , seems to be working with my latest fixes. I have checked on my profile: https://github.com/milaabl/milaabl-readme/actions/runs/5561652253/jobs/10159466961 Please check it out too |
Yes, it complete! |
Just noticed it on my profile too. Hmm, probably some attributes were retrieved incorrectly. Will have a look |
Still hava problem |
@SkyDynamic Thanks, I see. The problem is the y axis variable. The previous (currently broken) version built by @Platane uses the "y" attribute, but as there's no svg rect based chart data provided by GitHub anymore. Will try to figure it out, if anyone has any ideas -- your help is really welcome |
Did you figure out the solution? |
@pdqdat , not yet. I'm not sure how we can retrieve the y axis the new way, but will try to have a look at it tomorrow |
thanks for taking the time to edit a patch. I rather go with the github API solution, which is more stable. |
After an update, GitHub client returns the user's contributions as a table, instead of a generated svg. That's why there's a sudden build error in the workflow.
Please have a look @Platane . Should be fixed now! :)
Thanks