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: New PR from a fork does not get assigned to project #73

Open
lantisnt opened this issue May 19, 2021 · 0 comments
Open

Bug: New PR from a fork does not get assigned to project #73

lantisnt opened this issue May 19, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@lantisnt
Copy link

lantisnt commented May 19, 2021

When creating PR from a fork of the project, the PR doesn't get assigned to a project.
Action succeeds but fails internally:

changing col name for PR event
{
  "message": "Resource not accessible by integration",
  "documentation_url": "https://docs.github.com/rest/reference/projects#create-a-project-card"
}

https://github.com/lantisnt/ClassicLootManager/runs/2613102772?check_suite_focus=true
https://github.com/lantisnt/ClassicLootManager/actions/runs/854222956

That may be important info: That fork did not have this action in the code when the PR was requested (repo to which it was merged - the one i linked - had)

@srggrs srggrs added the bug Something isn't working label Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants