Does not seem to support "Beta" projects

[OliverRC]

Expected:

Define the name and location of "Beta" project to assign a card to an issue or PR.

Actual:

Does not find any projects. Only seems to find "classic" projects from my testing.

Attempts:

• Fully scoped PAT token
• Defining organization as project location

Logs:

##[debug]Inputs: {
##[debug]  token: '***',
##[debug]  projectLocation: 'my-org',
##[debug]  projectNumber: 0,
##[debug]  projectName: 'project-name,
##[debug]  columnName: '',
##[debug]  repository: 'my-org/repo-1',
##[debug]  issueNumber: 27
##[debug]}
##[debug]Projects list: []
##[debug]Projects: []
##[debug]Project: undefined
##[debug]'No project matching the supplied inputs found.'

[peter-evans]

Hi @OliverRC

You are correct, it doesn't.

This project uses GitHub's REST API, and unfortunately, the beta API seems to require using the GraphQL API. That means it's not straightforward for me to support this and the action needs a bit of work to make it happen.

When I have some time I will get around to doing this, but I can't promise anything soon. If anyone wants to take a shot at providing beta projects support, feel free, but please let me know in the comments.

[OliverRC]

I have made an implementation of assigning cards and custom fields via the GraphQL. I will have a look at maybe doing a PR or showing how I did it here when I am back at my work machine.

[peter-evans]

There is an official action, but it only seems to cover a simple case of adding a card to a project. It will be a useful reference to write this action's functionality for beta.
https://github.com/actions/add-to-project

[nullnik-0]

This project uses GitHub's REST API, and unfortunately, the beta API seems to require using the GraphQL API. That means it's not straightforward for me to support this and the action needs a bit of work to make it happen.

When I have some time I will get around to doing this, but I can't promise anything soon. If anyone wants to take a shot at providing beta projects support, feel free, but please let me know in the comments.

Hi, just wondering if this is still something that you are planning to do now that GitHub has sunset Projects (classic).

[peter-evans]

@nullnik-0 I'll try and take a look at this in the near future. The first thing I need to do is just check feasibility, and if the behaviour of this action will actually map well to the new projects.

[peter-evans]

After taking a look at the new projects today I'm not sure if this action makes sense anymore.

• The concept of "columns" is gone now. A card has "fields" and the project board view can be set to split items into columns by a field. It defaults to "Status."
• You can now configure quite detailed automation in the "Workflows" settings of a project. I would imagine that this covers a large number of use cases where this action was being used.

If anyone has any use cases where the combination of the official add-to-project action, and Project Workflows isn't sufficient, I would like to know.