github-project-automation-plus
github-project-automation-plus copied to clipboard
alex-page
Action Fails with GitHub Project Beta boards
I'm able to run this action successfully with a project board within the same repo as the action. When I attempt to use it for a Github Projects Beta board it fails to find it using the same access token. 🙁
I followed the README instructions from this repo when assigning permissions to the token and added a few extra just to rule that out in my debugging.
Is this limitation a known issue or does it make sense given your knowledge of access controls/API calls in regards to beta features?
Let me know what additional details I can provide to help debug this. I'm happy to create a PR to fix this as well depending on the complexity/scope of the change.
I haven't had a chance to make this work for the project beta. I think this is because the new projects live in organisations? If you want to contribute to make it work for both I would love to support it.
I think this is because the new projects live in organisations?
That would be my guess too.
I'll try to find some time to explore this in the next couple weeks. 🤞🏼
I just noticed this workflows tab in our GitHub project beta. This project might not be necessary in the future.
I'll hold off on this for a bit then and see what becomes of the new feature.
That does look promising.
Just wanted to add this token of information I came upon.
There is an issue for the Projects (beta) to automatically add new issues from a repository into projects (https://github.com/github/roadmap/issues/286). I picked this up from the roadmap, which suggests there are a lot of planned features including custom automation flows (https://github.com/github/roadmap/issues/281).
In the meantime, however, I don't think it's currently possible to automatically add issues to a project in Projects (beta) (https://github.com/github/feedback/discussions/5378#discussioncomment-1547434).
Fwiw, you can use octokit/graphql-action with beta boards although there is a bit more setup involved
I think this is because the new projects live in organisations?
That would be my guess too.
FYI, We've be successful using this action with org level project from a repository so it's seem the issue is specific to the new beta projects.
For anybody interested, you can automate your Beta boards with this here action: https://github.com/leonsteinhaeuser/project-beta-automations
Using it since a few weeks, works great
@phuhl Thanks for sharing! Can it also add PRs created by Dependabot to the beta boards?
@phuhl Thanks for sharing! Can it also add PRs created by Dependabot to the beta boards?
@hugovk Not sure, I had some issues with labels created by the API not triggering the label-events. But that really is a limitation of the Github API. The repository I linked basically does not handle the triggering, that's left up to you (but very easy to do, based on their README). Should you find out if it works with dependabot alerts, let me know :)