What's the meaning behind the "[*] => $e*" part?

Open
#4 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, go
Domain
cli, documentation

Research direction

Review the README's gst example and the referenced screencast, focusing on the output after the pipe. Determine what [*] => $e* represents, then clarify that meaning in the README so the documented output is understandable to users.

Written by the indexing model from the issue text.

Description

question ui

When I run gst I see some output that looks like this:

On branch: feature-branch  |  [*] => $e*

What does the part after the pipe indicate? I thought that maybe my terminal was failing to expand a variable somewhere, but I can see this included in the screencast & example output in the readme too.

PS. Thanks for creating scmpuff - I find it super-useful. :)

Dominant language
Go
Stars
419
Forks
30
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mroth/scmpuff

All issues in mroth/scmpuff

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.