Nejc Habjan

I'd say as long as we tie our resources to the API paths the difference in project / pipeline jobs is expected behavior, so I'll go ahead and close this...

Done in https://github.com/python-gitlab/python-gitlab/pull/2796.

> @Sjord very true, I would at least want to add support for `lazy=True` for GetWithoutIDMixin first so that this wouldn't require 2 API calls. > > The reason I...

I believe this was now merged as part of another PR. @JohnVillalovos if you think we missed something please reopen :bow: (I know some parts are disabled at the moment,...

@codejedi365 that's great, yeah actually going close to the node implementation would be the way to go IMO. At the time it made more sense to me to just revert,...

@travi sure, no rush. Thanks for considering this! The GitHub plugin issue seems slightly different in that it's more about duplicate comments in non-linear/multi-branch release workflows whereas this would be...

Sorry for the ping @DmitriyLewen. Are these types of parsers something you'd consider here? If not, I'd maybe look into creating standalone plugins. Thanks a lot!

Thanks for your response @DmitriyLewen! I understand. I was hoping it would maybe fit into the new `non-packaged` category that was recently introduced for unpackaged executables, see: https://github.com/aquasecurity/trivy/blob/5bb3a47e03e0156a7949dfd453908798eb8a0b65/pkg/fanal/analyzer/const.go#L77-L80 However, I'll...

That's great, I'll give that a shot :)

> The only work around I can think to allow modifying branch permissions is for the user to GET `protectedBranch`, implement their own translation code from `push_access_levels` structure to the...