search

benthayer / git-gud

Wanna git gud? Then get git-gud, and git gud at git!
MIT License
401 stars 42 forks source link

Implement Basics Status Message #310

Closed sahansk2 closed 3 years ago

sahansk2 commented 3 years ago

Fixes #267

sahansk2 commented 3 years ago

Strange, I thought I posted a comment... I split everything into multiple different functions -- target_branch_str can probably be moved into Operator, but display_tree_content and display_commit_content together make up the "basics status message". We can directly invoke display_tree_content for working/staging, and we can use display_commit_content for displaying all commits.

sahansk2 commented 3 years ago

@benthayer This is ready for review again. Feel free to get rid of commit 8a3585fa360f176d1c3177944a9227f8900e2f49 if it seems out of place, it's just there to make sure that the functions don't unexpectedly crash during development.

benthayer commented 3 years ago

Should be all good. I still want to refactor the user messages:

gitgud.skills.user_messages.py -> gitgud.user_messages.__init__.py
gitgud.skills.state_messages.py -> gitgud.user_messages.stateful.py