You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.
A simple git commit and mroe elaborate poetry install pair of examples below.
It's common to announce more of the work that you do.
This is useful for debugging.
And it's useful to assist people with learning what their tools do.
But it's also just good practice and more aesthetically enjoyable (think Centre Pompidou in Paris) to show your work. To show the activity being done and let people appreciate it.
e.g. even simple start & completion messages that give info like n template points filledgit initialized pre-comit hooks set to executable and moved to .git/hooks/ dir, git add . && git commit --message ...
^ maybe something a bit nicer, but just noting the steps completed.
Granted, the creation is almost instantaneous. So not adding too much time to display is wise, but dropping what's going to happen and what happened text is likely to be a significant user experience improvement.
The text was updated successfully, but these errors were encountered:
A simple
git commit
and mroe elaboratepoetry install
pair of examples below.It's common to announce more of the work that you do.
This is useful for debugging.
And it's useful to assist people with learning what their tools do.
But it's also just good practice and more aesthetically enjoyable (think Centre Pompidou in Paris) to show your work. To show the activity being done and let people appreciate it.
e.g. even simple start & completion messages that give info like
n template points filled
git initialized
pre-comit hooks set to executable and moved to .git/hooks/ dir
,git add . && git commit --message ...
^ maybe something a bit nicer, but just noting the steps completed.
Granted, the creation is almost instantaneous. So not adding too much time to display is wise, but dropping what's going to happen and what happened text is likely to be a significant user experience improvement.
The text was updated successfully, but these errors were encountered: