You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because module standardiser will only update supported repos, it fail to remove supported badges from the README.md of unsupported repos because it won't run script on it
First we need to clarify that we indeed should not display the supported badge on things that are only supported for cms 4. If we do still want a badge then it should be a different badge IMO that says supported for security only
Acceptance criteria
Update module-standardiser to remove the supported badge from unsupported modules.
Only the CMS 5 branches should be updated.
All modules that lost their supported status in CMS 5 should loose their badge.
I'm happy to remove badges once support is dropped by the latest major.
I guess if we want to be especially formal about this, we could remove the badge from the default branch, but keep it on the branches where the module was supported.
Because module standardiser will only update supported repos, it fail to remove supported badges from the README.md of unsupported repos because it won't run script on it
Ckan registry still has a supported badge on it despite it not being supported for cms 5, though it is supported for cms 4
To decide
First we need to clarify that we indeed should not display the supported badge on things that are only supported for cms 4. If we do still want a badge then it should be a different badge IMO that says supported for security only
Acceptance criteria
PRs
The text was updated successfully, but these errors were encountered: