-
Notifications
You must be signed in to change notification settings - Fork 23
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
Receive #ERROR# TypeError: Cannot read property 'columns' of null
on run.
#15
Comments
Your project URL needs to have the actual owner and repo names, something like:
If the URL is correct, you should see output that says something like |
Oh - yes, I've just redacted the owner and repo names in the example config and logs here as it's a private repo. The URL in the real config is correct, and yep, I get that output in the logs. So I don't think that's the issue. Any other ideas? |
Had the same issue. For people finding this old issue in the future: |
@benjamin-hull Did you find a fix for this? @emre1702 This did not change the error for me. |
Dear all, I have the same error: Any news about it? |
I am getting the same error :
... could it be because this a new project, and by new I mean the newer version of GitHub Projects, the legacy ones being discontinued? |
I am also having the same error currently. I have a suspicion you are correct @fredericsimard but I'm hoping you're incorrect lol 😓 😅 |
@colinwilliams91 I believe this might fix the issue. I'll try that tomorrow and let you know. |
@colinwilliams91 Turns out there is no need for an action with the new Projects, you can use Workflows to move issues and PRs in a project and put them in a specific column. More details here: |
I'm trying to set up this action on a private repo, and receive the following log on run:
My workflow YAML looks like this:
The project URL is definitely correct, as are the names of the columns and labels.
This is my first attempt at using actions, so I could be missing something. Any ideas? Thanks in advance!
The text was updated successfully, but these errors were encountered: