Beta Github Projects not showing up in Plugin Project

[KingNexu]

Do I have to change the setup, or is this still not supported?

[lowlighter]

Hi !

Not yet supported, but support could be added

[KingNexu]

How smart would it be to change it now, as the Projects are still in Beta?

[lowlighter]

We can support both versions while GitHub still support both

And while the new projects are still in beta, supporting at least common features is safe I guess

I didn't check yet what exactly is different from the classic projects so I can't tell how much work/maintenance it would implies yet

[lowlighter]

There's a pretty basic support for beta projects right now on the master branch, but from what I've seen, should be doable to add other features like assignee, labels, milestones etc.

Not sure if there is a progress tracking on new projects though

[Gregor7008]

Idk how these discussions work yet, so I'll write this here:
I got the same problem, but I have the "Licenses" field appended and it's showing me the "Unexpected error" message as well. I guess this is because on "Active projects" the rendering engine failed and then didnt restart for "Licenses", correct?
If so: Perfect, just have to wait for an update for Projects V", if not... Well I have to get to it again...

This is how it looks btw.

Edit: Creation of an official issue on this planned?

[Gregor7008]

Okay, changed and tested the action again: It works!

Okay, except for the licenses plugin...

{name: 'licenses',
 result: {
    error: {
       message: 'Unexpected error',
       instance: 'npm ERR! The `npm ci` command can only install with an existing package-lock.json or\n' +
       'npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or\n' +
       'npm ERR! later to generate a package-lock.json file, then try again.\n' +
       '\n' +
       'npm ERR! A compl'... 104 more characters
     }
  }
}

And also: Long issue titles extend over the images border, idk whether that was a thing with the old projects as well, but I'm only here ot report it. Tbh it's kind of my fault to give issues such long titles 😅!
Regardless: Thanks for the quick help and even the even quicker implementation!

[lowlighter]

For the license plugin, seems to be to be a compatibility issue with the package-lock.json.

From the error logs, I think just changing the plugin_licenses_setup command to npm install should work, but maybe npm install -g npm@latest && npm ci could also work

---

As for the display issue in the project plugin, probably missing a text-overflow: ellipsis somewhere, shouldn't be too hard to fix

Don't hesitate to report any other issues you encounter, feedback is always appreciated 😄

[Gregor7008]

Tested both npm install and npm install -g npm@latest && npm ci, but I'm still getting the same error.

And for the feedback: I like watching my favourite things improving, so I'll report any problem asap (Ofc taking into consideration, that the error is in front of the screen 😅)!

[lowlighter]

I didn't understand that your project was not a nodejs one 😅

npm is a tool used to install dependencies with node projects (which is configured through a package.json), which is why the above commands don't work

---

github/licensed requires your project dependencies to be installed/cached which is why plugin_license_setup option exists. In your case though, I don't think you have anything to setup to you can just omit it. Also, your repository doesn't have a default license file, so the output will probably empty too 😄

[Gregor7008]

Well, that fixed it!

Thanks!