Skip to content
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

[BUG] Invalid status code:128 #129

Closed
Key5n opened this issue Jan 13, 2023 · 6 comments
Closed

[BUG] Invalid status code:128 #129

Key5n opened this issue Jan 13, 2023 · 6 comments

Comments

@Key5n
Copy link
Contributor

Key5n commented Jan 13, 2023

Describe the bug
like #113 #104 ,Running github actions, my workflow said invalid status code:128.

I fixed this problem by giving "Read and write permission to GITHUB_TOKEN" like below.
But I can't miss why I got stuck although followed your tutorial.
github_profile_summary_fixed

It seems that it couldn't commit and push updated contents.
Do you know the reason? I am new to Github Actions.

To Reproduce
Steps to reproduce the behavior:
Follow your tutorial

Expected behavior
Finish tutorial

Screenshots
github_profile_summary_cards_failure

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Firefox
  • Version 108.0.2
@vn7n24fzkq
Copy link
Owner

Hi @Key5n , sorry for the late reply.
Can you re-trigger the workflow?
For some reason, the git push failed sometimes.

@Key5n
Copy link
Contributor Author

Key5n commented Jan 15, 2023

Thank you for the reply.
I re-triggered it with no default write permission to GITHUB_TOKEN.
But I faced the same error.
I also followed the tutorial again, but nothing has changed.

With default write permission to GITHUB_TOKEN, it succeeded though.

@vn7n24fzkq
Copy link
Owner

Great!
Seems we missing that permission in the document.
Thanks for the issue.

@cimadai
Copy link

cimadai commented Feb 14, 2023

I faced to same issue and finally I succeeded to push with select Read and write permissions in Workflow permissions section.

@Key5n
Copy link
Contributor Author

Key5n commented Feb 14, 2023

Yes, that is another solution.
If you mind giving read and write permission to GITHUB_TOKEN for all-scopes, we can avoid this by only adding content: read permission to the job.
I verified it works on my repository.

@vn7n24fzkq
Copy link
Owner

Great! I think that is a better solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants