search

carloscuesta / gitmoji

An emoji guide for your commit messages. 😜
https://gitmoji.dev
MIT License
15.74k stars 799 forks source link

Gitmoji Django recommendations #1487

Closed paduszyk closed 1 year ago

paduszyk commented 1 year ago

Discussion

Hi!

The project is great! I really like to use it!

I currently work with Django I was wondering are there any recommendations on how to use Gitmojis to specific parts of this framework, e.g. updates of models, admin options, forms, views, etc.

If anyone wants to share the ideas, please comment.

Best regards!

Validations

carloscuesta commented 1 year ago

Hey there!

Thanks for your interest in Gitmoji! I'm happy to hear that you're enjoying the project and finding it useful.

When it comes to using Gitmojis with Django, we want to make sure that Gitmoji remains a tool that can be used by anyone, regardless of the language or framework they're working with. Our goal is to keep it language agnostic, so that it can be a valuable resource for developers across different platforms.

I'm pretty sure you can apply a lot of emojis that are part of the convention, feel free to explore them in the website: https://gitmoji.dev

paduszyk commented 1 year ago

I totally agree - Gitmoji should be seen as a tool for any framework, language, etc. I was just wondering which Gitmoji is used Django developers to mark some standard task.

For example: database tables are represented in Django by classes called models (so, the types actually). So, is an update of a model database related update (🗃️), or type update (🏷️), or bussiness logic (👔)?

carloscuesta commented 1 year ago

I totally agree - Gitmoji should be seen as a tool for any framework, language, etc. I was just wondering which Gitmoji is used Django developers to mark some standard task.

For example: database tables are represented in Django by classes called models (so, the types actually). So, is an update of a model database related update (🗃️), or type update (🏷️), or bussiness logic (👔)?

Hey!

I believe everyone should be categorising the commits in the same way following the description of each gitmoji irregardless of the framework they're using

But answering your question:

So, is an update of a model database related update

I would use :card_file_box: for database related changes. To me in that particular context the types and the business logic makes no sense at all given that you have one for the database.

You may want to read: https://github.com/carloscuesta/gitmoji/issues/1334

carloscuesta commented 1 year ago

Hey! I'll close this issue given that after a week we don't have any other opinions!