[Bug]: Error Code 128

[Gr8z]

I am getting the following error when I try to run this action with my RSS feed:

{"code":128,"outputData":""}

action.yml

      - uses: gautamkrishnar/blog-post-workflow@master
        with:
          feed_list: "https://dohad.dev/feed.xml"

[gautamkrishnar]

hi @Gr8z i cannot reproduce this on my test repo.

Please dont combine the workflow with wakatime readme workflow. Just create a new .github/workflows/blog-post-workflow.yml and add the code there.

[gautamkrishnar]

Also there is a mistake in your code. This workflow requires checkout action to be included. Please check the docs before using the workflow:
https://github.com/gautamkrishnar/blog-post-workflow#how-to-use

You missed:

- uses: actions/checkout@v2

This is the main reason why the workflow is failing in your repo.

[guangzhengli]

I used uses: actions/checkout@v2, but it still not work.

Finally, I found it needs to open workflows write permissions in Setting -> Actions

[gautamkrishnar]

@guangzhengli it is working now https://github.com/guangzhengli/guangzhengli/runs/7825931241?check_suite_focus=true it might be because of the wrong secrets.GITHUB_TOKEN you had given.

[Danie10]

I had exactly the same issue here - think this permissions setting needs to be mentioned in readme.md. It may not be an issue for those who already had work flows, but for first time creators, this is going to trip them up.

[gautamkrishnar]

@Danie10 I never personally received this issue in my account. As far as I know, the workflow permission option is by default "read and write", unless you manually changed it. Are you sure that you are able to reproduce this issue on all new accounts and repos?

Update, tried creating a new repo it is also by default r/w:

Anyway, I had added the same to the readme so that people can know: 020f63d

[Danie10]

This is the first time I created an action, so no it was a default on my account. I never even knew about it until today. But after I allowed the permissions it now works fine.

…

On Sat, 01 Oct 2022, 00:54 Gautam krishna R, ***@***.***> wrote: @Danie10 <https://github.com/Danie10> I never personally received this issue in my account. As far as I know, this option is by default read and write, unless you manually changed it. Are you sure that you are able to reproduce this issue on all new accounts and repos? — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIZVPXG3S65MVEOEFP4NNDWA5VSLANCNFSM45YDZXPA> . You are receiving this because you were mentioned.Message ID: ***@***.***>