Rename "Project Service" to be more generic
Problem to solve
As we move towards Mass integration at the group and instance level, "Project services" are increasingly mis-named. A "Project service for a group" is really weird.
The following makes sense when it's on a Project Settings
page, but what happens when this functionality is available at the group too?
Further details
- Whatever name we go with shouldn't include "projects"
- "services" can mean other things in other contexts
Candidate names
- Integrations
- Services
- Something else? Say so in the comments!
Proposal
- Update places in the UI where we refer to
Project Services
(i.e. onhttp://gitlab.com/<group>/<project>/-/settings/integrations
) - Update the docs to scrub any reference to this and change to new name
- Change names in the codebase to reflect new naming
Edited by Patrick Deuley