Skip to content
This repository has been archived by the owner on Dec 31, 2021. It is now read-only.

Bypass comment posting from forked repository context #42

Open
Ash258 opened this issue Aug 4, 2019 · 4 comments
Open

Bypass comment posting from forked repository context #42

Ash258 opened this issue Aug 4, 2019 · 4 comments
Assignees
@Ash258
Labels
bug Something isn't working future-release high-priority pull-request-action

Comments

@Ash258
Copy link
Owner

Ash258 commented Aug 4, 2019

When PR is created from forked repository initial API call suffer from Resource not accessible by integration

Now:
https://github.com/Ash258/GithubActionsBucketForTesting/runs/184991649

Before:

Ash258/GithubActionsBucketForTesting#66
@Ash258 Ash258 added bug Something isn't working pull-request-action labels Aug 4, 2019
@Ash258 Ash258 added this to the 1.0.0 milestone Aug 4, 2019
@Ash258 Ash258 self-assigned this Aug 4, 2019
@Ash258
Copy link
Owner Author

Ash258 commented Aug 8, 2019

This needs to be at least clarified in version 1.0.0.

@Ash258
Copy link
Owner Author

Ash258 commented Sep 14, 2019 •
edited
Loading

https://help.github.com/en/articles/events-that-trigger-workflows#pull-request-events-for-forked-repositories

The permissions for the GITHUB_TOKEN in forked repositories is read-only. For more information about the

Secrets are not passed to workflows that are triggered by a pull request from a fork of this repository.

Ash258 added a commit that referenced this issue Sep 16, 2019
@Ash258
Export PR state to own function #42
7abdeb5
@Ash258 Ash258 changed the title Investigate problem with PR comments posting Bypass comment posting from forked repository context Oct 12, 2019
@Ash258
Copy link
Owner Author

Ash258 commented Oct 12, 2019

Workaround needs to be investigated.

@Ash258 Ash258 removed this from the 1.0.0 milestone Oct 12, 2019
@Ash258
Copy link
Owner Author

Ash258 commented Jan 11, 2020

PR created from template with label verify, could fire up two actions.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Ash258 Ash258

Labels
bug Something isn't working future-release high-priority pull-request-action
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Ash258