Serializing web_based_commit_signing_enabled leads to N+1 queries
-
web_based_commit_signing_enabledis a cascading setting (see: https://docs.gitlab.com/development/cascading_settings/)- This means that ancestor values (groups) are considered when trying to read this value from the project
- This leads to N+1 queries when the value is serialized for multiple projects (e.g in a graphql query)
- This means that ancestor values (groups) are considered when trying to read this value from the project
Edited by 🤖 GitLab Bot 🤖