-
Notifications
You must be signed in to change notification settings - Fork 112
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
CI: WebAssembly action failed when PR merged #400
Comments
ChinYikMing
added a commit
to ChinYikMing/rv32emu
that referenced
this issue
Apr 5, 2024
ChinYikMing
added a commit
to ChinYikMing/rv32emu
that referenced
this issue
Apr 5, 2024
The existing WebAssembly CI works on my repository, but it is failed here. This is very strange but we still have to solve it. Combining some dicussion in github-push-action's issue and my own thought, when checking out demo, the persist-credentials is set to false, thus the token used for further action should be specified. See issue: sysprog21#400
ChinYikMing
added a commit
to ChinYikMing/rv32emu
that referenced
this issue
Apr 5, 2024
The existing WebAssembly CI works on my repository, but it is failed here. This is very strange but we still have to solve it. Combining some dicussion in github-push-action's issue and my own thought, when checking out demo, the persist-credentials is set to false, thus the token used for further action should be specified. See issue: sysprog21#400
jserv
pushed a commit
that referenced
this issue
Apr 5, 2024
The existing WebAssembly CI works on personal repository, but it failed here. This is very strange but we still have to solve it. Combining some discussion in github-push-action's issue and my own thought, when checking out demo, the persist-credentials is set to false, thus the token used for further action should be specified. See issue: #400
ChinYikMing
added a commit
to ChinYikMing/rv32emu
that referenced
this issue
Apr 5, 2024
See issue: sysprog21#400
To access the secrets variable (or token) in actions when merging PR, it is necessary to use |
ChinYikMing
added a commit
to ChinYikMing/rv32emu
that referenced
this issue
Apr 5, 2024
To access the secrets variable (or token) in pull request event, it is necessary to use pull_request_target instead of pull_request. Close: sysprog21#400
jserv
pushed a commit
that referenced
this issue
Apr 5, 2024
To access the secrets variable (or token) in pull request event, it is necessary to use pull_request_target instead of pull_request. Close: #400
vestata
pushed a commit
to vestata/rv32emu
that referenced
this issue
Jan 24, 2025
To access the secrets variable (or token) in pull request event, it is necessary to use pull_request_target instead of pull_request. Close: sysprog21#400
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See action
The text was updated successfully, but these errors were encountered: