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

add usage-strings ci check and amend remaining usage strings #1147

Closed
wants to merge 2 commits into from
Closed

add usage-strings ci check and amend remaining usage strings #1147

wants to merge 2 commits into from

Commits on Feb 25, 2022

  1. amend remaining usage strings according to style guide 

    Usage strings for git (sub)command flags has a style guide that
suggests - first letter should not capitalized (unless required)
and it should skip full-stop at the end of line. But there are
some files where usage-strings do not follow the above mentioned
guide.

Amend the usage strings that don't follow the style convention/guide.

Signed-off-by: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
    @Abhra303
    Abhra303 committed Feb 25, 2022
    Configuration menu
    Copy the full SHA
    dc200d0 View commit details
    Browse the repository at this point in the history

  2. parse-options.c: add style checks for usage-strings 

    `parse-options.c` doesn't check if the usage strings for option flags
are following the style guide or not. Style convention says, usage
strings should not start with capital letter (unless needed) and
it should not end with `.`.

Add checks to the `parse_options_check()` function to check usage
strings against the style convention.

Signed-off-by: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
    @Abhra303
    Abhra303 committed Feb 25, 2022
    Configuration menu
    Copy the full SHA
    e1c5a32 View commit details
    Browse the repository at this point in the history