You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the snake animation, I have checked out the website and when it generates the "snake.yml" file the branch name is "master". For this reason I was stuck at that for 1 complete day and then, I changed the named to "main" branch and it worked. So, I think it will be better to change it to "main" branch or doing it like this "branches: ["master", "main"]".
To make a README file choose the second template or to make a custom one choose the snake animation.
Click on "Generate README".
The README generated will be along with "snake.yml" file.
Open the "snake.yml" file and copy it.
Copy it in the workflows of your GitHub.
Change the necessary parts like "Github token", "Username", etc.
Also the branch need to be changed from "master" to "main" (bug).
What were you expecting to happen?
I was expecting to run the snake animation on my GitHub profile but it wasn't doing the same and when I changed the name of the branch from "master" to "main" it worked.
Additional information about your environment
Device: Laptop
OS: Windows 11 home
Browser: Chrome
Additional context
No response
The text was updated successfully, but these errors were encountered:
What happens?
For the snake animation, I have checked out the website and when it generates the "snake.yml" file the branch name is "master". For this reason I was stuck at that for 1 complete day and then, I changed the named to "main" branch and it worked. So, I think it will be better to change it to "main" branch or doing it like this "branches: ["master", "main"]".
What are the steps to reproduce this issue?
What were you expecting to happen?
I was expecting to run the snake animation on my GitHub profile but it wasn't doing the same and when I changed the name of the branch from "master" to "main" it worked.
Additional information about your environment
Additional context
No response
The text was updated successfully, but these errors were encountered: