-
-
Notifications
You must be signed in to change notification settings - Fork 552
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
FEAT: Add Symbol style customized by the user (Help with PR) #490
Comments
Hi @caupolicanre, the GH actions may run by Docker image. Please add a debug log to check. |
@oHTGo The debug log you mention is done by using the "DEBUG_LOGGING" enviroment variable in the yml workflow file? or is it a configuration in Docker? I have very little experience working with docker. I just tried enabling DEBUG_LOGGING in the workflow file, here is the job with the debug messages. Should I modify "action.yml" file? |
I just fixed. The problem was that the action.yml file was using: runs:
using: 'docker'
image: 'docker://wakareadmestats/waka-readme-stats:master' I modified it to run and test my action with "Dockerfile" file located in root repository: runs:
using: "docker"
image: "Dockerfile" |
Hi, I requested a new symbol to be added in #489, then I wanted to be able to enter any type of symbol in the yml workflow file.
I'm trying to improve the symbol logic, but I keep getting the same error.
First I tried the same logic as the action shows, and did the same as shown in #471, but when I run the action, I receive the same KeyError.
Then I tried using waka-readme logic for handling symbols entered by the user with an enviroment variable. With this implementation, the action works fine, but nothing changes.
I modified the function "make_graph" and using the previous enviroment variable mentioned, check, if it's empty, use "Symbol" class, but if it is not, use the symbol entered by the user.
This is the workflow file:
In this 2 commits are the modifications I made:
make_graph function logic
enviroment variable
The text was updated successfully, but these errors were encountered: