Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

git-elegant:90: Describe usage of git elegant #118

Closed
0pdd opened this issue May 11, 2018 · 1 comment
Closed

git-elegant:90: Describe usage of git elegant #118

0pdd opened this issue May 11, 2018 · 1 comment
Assignees
@extsoft

Comments

@0pdd
Copy link

0pdd commented May 11, 2018

The puzzle 6-8bd69a57 from #6 has to be resolved:

elegant-git/src/main/git-elegant

Line 90 in 85b0d75

# @todo #6 Describe usage of git elegant

The puzzle was created by Dmytro Serdiuk on 11-May-18.

Estimate: 0 minutes,

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.
0pdd referenced this issue May 11, 2018
@extsoft
Update links for tool badges
85b0d75
@0pdd 0pdd mentioned this issue May 11, 2018
Closed
@extsoft extsoft mentioned this issue Aug 12, 2019
Closed
@extsoft extsoft added this to the 0.5.0 milestone Sep 1, 2019
@extsoft extsoft self-assigned this Sep 1, 2019
@extsoft extsoft removed this from the Top priority milestone Sep 9, 2019
extsoft added a commit that referenced this issue Sep 11, 2019
@extsoft
Add initial tests for specific logic of git-elegant.bash
c20aa82 
The tests handle unknown and non-provided commands. They allow making
some refactoring of git-elegant.bash.

In general, the tests for git-elegant.bash have to cover a logic of
invocation of other commands or some corner cases.

#118
extsoft pushed a commit that referenced this issue Sep 11, 2019
Add help messages for each Elegant Git command
b04fb48 
`-h`, `--help`, `help` are allowed options to get a help message for any
command. The `libexec/git-elegant` is responsible for building and
printing help. The commands scripts are responsible for providing the
messages. It is described on "Architecture" section of README.md.

Also, there are new tests which allow checking of the availability of the
help messages.

#118
extsoft pushed a commit that referenced this issue Sep 11, 2019
Read available commands dynamically
243adfe 
`git elegant commands` will read commands dynamically. This change
allows having more stable results of other tests as the `commands`
command is often used in other commands or tests. For instance,
if we add a new command, it will be found automatically and
1. a help will be verified for it
2. `tests/git-elegant-commands.bats` will fail by requiring updates with
the data about the new command.

#118
extsoft pushed a commit that referenced this issue Sep 11, 2019
Generate docs/commands.md based on CLI help
b7ceba6 
This will significantly simplify the process of documentation updates.
Also, there is configured verification step which checks if
documentation is re-generated for fresh changes. This will guarantee
that we always will have up-to-date documentation for the commands
(most updated file).

#118
extsoft added a commit that referenced this issue Sep 11, 2019
@extsoft
Add help messages for each Elegant Git command
10594a7 
`-h`, `--help`, `help` are allowed options to get a help message for any
command. The `libexec/git-elegant` is responsible for building and
printing help. The commands scripts are responsible for providing the
messages. It is described on "Architecture" section of README.md.

Also, there are new tests which allow checking of the availability of the
help messages.

#118
extsoft added a commit that referenced this issue Sep 11, 2019
@extsoft
Read available commands dynamically
98a0ed8 
`git elegant commands` will read commands dynamically. This change
allows having more stable results of other tests as the `commands`
command is often used in other commands or tests. For instance,
if we add a new command, it will be found automatically and
1. a help will be verified for it
2. `tests/git-elegant-commands.bats` will fail by requiring updates with
the data about the new command.

#118
extsoft added a commit that referenced this issue Sep 11, 2019
@extsoft
Generate docs/commands.md based on CLI help
9fc4770 
This will significantly simplify the process of documentation updates.
Also, there is configured verification step which checks if
documentation is re-generated for fresh changes. This will guarantee
that we always will have up-to-date documentation for the commands
(most updated file).

#118
@extsoft extsoft mentioned this issue Sep 11, 2019
Merged
4 tasks
extsoft added a commit that referenced this issue Sep 11, 2019
@extsoft
Generate docs/commands.md based on CLI help
449668e 
This will significantly simplify the process of documentation updates.
Also, there is configured verification step which checks if
documentation is re-generated for fresh changes. This will guarantee
that we always will have up-to-date documentation for the commands
(most updated file).

#118
@0pdd
Copy link
Author

0pdd commented Sep 12, 2019

The puzzle 6-8bd69a57 has disappeared from the source code, that's why I closed this issue.

@0pdd 0pdd closed this as completed Sep 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@extsoft extsoft

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@extsoft @0pdd