Remove Security Advisory banner from non-code related projects

Don't think there is an easy way to distinguish code or none code projects as the "node" this is created under is probably module project. In the end, any project being code or none code get's a space on GitLab, so technically, it could contain code. https://git.drupalcode.org/project/artificial_intelligence_initiative

I guess the fastest way is to opt-in into the advisory, even though there might never be a single line of code or stable release being tagged which would enlist it as covered.

Just wondering, why is this not a page on the documentation system, and the "project" just for tracking issues/credits? That way, one would not need to market the project page but the documentation page instead.

I wanted to say the real solution would be to be able to create a project without git repository. But with the Drupal.org issue queue becoming gitlab issues, that will become redundant before it's even implemented.

e.g. we have this "hack" on https://www.drupal.org/project/contribution_events → which has no code at all.
I tink for issue credits/visibility, a project page (of any kind) is a good thing to have issues available.
I also don't think, that there is an easy way for now.
But I would also find it super pleasant, if projects, without code, could not have this banner.
Maybe there could be a check: if there is no repository code, then the banner is hidden…

Drupal.org does not track Git repository contents, we don’t have a quick way to programmatically know if a project has code or not. Some community projects use their Git repository for charters or other information, so a project having “code” is not necessarily a great check. Adding the ability to make projects without repositories would be extra work for little useful functionality and more edge cases.

I guess the fastest way is to opt-in into the advisory, even though there might never be a single line of code or stable release being tagged which would enlist it as covered.

This is the best way for these projects to move forward.

Moving this to the AI initiative project.

Hi @anoopjohn,
I think issue should move back to previous project, as I understand, there is nothing I can do, there is no checkbox I could click or smth. Also it is general feature request for drupal.org

I guess the fastest way is to opt-in into the advisory, even though there might never be a single line of code or stable release being tagged which would enlist it as covered.

This is the best way for these projects to move forward.

Unclear what that is

I see I also got previously a private message from @anoopjohn with more explanation.

I checked I don't have such permissions, and I don't have plans to apply, as that is a separate process when upgrading a module to a stable state.

Today I highly simplified project description, with main focus to link users to AI module, as that is there the action is.