How to Properly Use ✨ on a Backend using Clean Architecture

Discussion

I've been using Gitmoji for a few months, but there is a topic I always end up discussing with my colleagues, and each one have different opinions. Basically, when creating a new user feature on the backend ,we have a controller, a Service, a Repository, and sometimes a procedure. Let's say I have to create a endpoint to get data from some table.

I usually create a commit with the procedure using 🗃️.
Then I create a commit with the get method calling and retrieving the procedure's data, what should be the emoji here? 🗃️, ✨, 🚧 , 🏷️, 👔?
Then I create a method in the service to retrieve the data using the repository.Get method, again, what should be the correct emoji?
And in the last commit, I create the Controller with the Get route, some of my colleagues suggests that only the controller commit should have ✨, since it's exposing the feature to external clients. In my opinion the service and repository public methods are also features, so I'm not sure what should be the correct approach here.

Validations

[x] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue requesting the same feature.

carloscuesta / gitmoji

How to Properly Use ✨ on a Backend using Clean Architecture #1669

Discussion

Validations