Is there any reason to prevent updates screenshots on the forked pull request? #1821
Replies: 3 comments 2 replies
-
Hi @Jaehwa-Noh, what do you mean? nowinandroid/.github/workflows/Build.yaml Lines 81 to 103 in a0f2786 The only thing is you have to have a PR opened in your fork for this worfklow to run in the context of your fork. You can easily do that by changing the "base" when creating a PR. |
Beta Was this translation helpful? Give feedback.
-
After a brief search, I get here and here. The reason is there's no way to do this with a secure way. |
Beta Was this translation helpful? Give feedback.
-
But also it's very easy to create a PR in your fork and let your action add the screenshots. |
Beta Was this translation helpful? Give feedback.
-
It made that decreasing a productivity.
Contributors have to update manually with a new redundant own forked their repository only for updating screenshots and have to waiting CI took it.
Any reasons that needs to prevent update the screenshots on a forked pull request?
Related #1697
Beta Was this translation helpful? Give feedback.
All reactions