-
Notifications
You must be signed in to change notification settings - Fork 93
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
Project not found - Classic project #81
Comments
I have a similar problem here, only in a private context... I'm trying to automate moving issues for a project within an organization. The repository and project are private. What am I doing wrong? I configured the personal access token scopes in the link: My workflow is set up in an even simpler way: name: "Foo"
on:
issues:
types: [opened]
jobs:
automate-project-columns:
runs-on: ubuntu-latest
steps:
- uses: alex-page/github-project-automation-plus@v0.8.1
with:
project: Foo
column: Bar
repo-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} I've also enabled SSO on the token... Screenshot: |
Any up ? We got the same issue for organization, it can't found the project, even with good permission of token. |
@SirMishaa Here you can see a working example I made in the past for the Vapor organisation https://github.com/vapor/ci/blob/main/.github/workflows/issues-to-project-board.yml |
I have this same problem, and I looked at the action failure logs. Looks like Node.js needs an upgrade, although I'm pretty new to all this so not sure if it's something I can do on my end or the action code's end. Edit: Just saw this in another thread, I guess it's not really needed that much anymore. #76 (comment) I'd love to see if it's possible to have our own custom actions though, would really open up quite some new workflow ideas with the custom fields that we can add in projects I believe. |
@Neehal-ATD this action supports NodeJS 16 as a minimum. See the latest commit into the repository. |
@alex-page Ah ok I think I found the issue; I'd copied the code from the examples you had on the GitHub Marketplace page which had v0.8.1 listed in the syntax, not 0.8.2. 🤦♂️I didn't really check if it was the latest version. |
Updated the docs. Thanks Neehal! |
@wnqueiroz, were you able to get the workflow to work? I get the same error as you did when I tried to use the workflow to move issues to a project in a private organization.
|
Same issue as @wnqueiroz and @steph-crown . |
Also ran into this with |
I don't know how to solve this problem, I would have to dig through the API docs and replicate it myself. There might be some issues with the logic to find projects as it is meant to check your org and own repos. This might have been changed recently. |
There is a possibility that this issue arises when using it with Beta projects. |
Is this action working with the new projects? I don't believe they're beta anymore. They are called Github deprecated the classic projects and it won't let you create new ones unless you already have existing classic projects. Thanks |
The new projects have a lot of automation already built into them. I am unsure if this action is needed for them. |
same issue with 0.8.3
|
I looked into it and the new projects will require new GraphQL queries. The query used by this action only return classic projects. I could not create a classic project, so the project I have created is V2.
And the response was:
Meaning the column info is now in options of a Status node in the project. This seems pretty different to the way columns are obtained with classic projects. I would think it means some important changes are necessary to make this action work with project V2. |
I've discovered that 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:
Hope this can help others! |
So I have been working on creating a workflow to put issues with the good first issue label onto a project board.
I've managed to make this work in an organisation, but it doesn't seem to work when using a public repository with a user project not belonging to an organisation.
https://github.com/BennyDeBock/test-gh-actions/runs/7598890181?check_suite_focus=true
https://github.com/users/BennyDeBock/projects/1/views/1
Here is the workflow I'm using.
https://github.com/BennyDeBock/test-gh-actions/blob/main/.github/workflows/project-board.yml
Is there something I'm doing wrong? or somewhere that i'm able to specify the url to the project?
@alex-page
The text was updated successfully, but these errors were encountered: