Tell us about your incident:
A clear and concise description, 'what is your incident?'
-> there is an issue when a --filename is used more than once in repository
-> there is an issue that '/' can not be included in --filename because --filename could of been used as a workaround when there is more than one --filename in the repository
-> add a prompt or user help when there are more then one --filename in the repository
To reproduce your incident:
Steps to reproduce your incident:
- Enter -> git-TEST-cases.sh --filename FVT-setup.sh --add
Actual results:
If applicable, add screenshots to help explain your incident.
->
272201 uadmin@five-rpi3b: ~/github/BradleyA/markit/TEST/find-code.sh
A> git-TEST-cases.sh -f FVT-setup.sh --add
/usr/local/bin/git-TEST-cases.sh: line 268: cd: ./TEST/find-code.sh/FVT-setup.sh
./hooks/EXAMPLES/FVT-setup.sh
./hooks/bin/TEST/git-TEST-cases.sh: No such file or directory
On branch master
Your branch is ahead of 'origin/master' by 1 commit.
(use "git push" to publish your local commits)
Untracked files:
testfiles/version.m4
testfiles/version.sh
testfiles/version.tmp
nothing added to commit but untracked files present
/usr/local/bin/git-TEST-cases.sh: line 281: cd: ./TEST/FVT-setup.sh
./hooks/EXAMPLES/TEST/FVT-setup.sh: No such file or directory
INFO: If filename is not found. Check spelling of filename
or try git-TEST-cases.sh --filename <FILE_NAME> --hooks
or try git-TEST-cases.sh --help
./TEST/find-code.sh/FVT-setup.sh
./TEST/markit/FVT-setup.sh
./TEST/FVT-setup.sh
./TEST/FVT-setup.sh/SA-cleanup.sh
./TEST/FVT-setup.sh/SA-setup.sh
./TEST/FVT-setup.sh/SA-shellcheck-001.expected
./TEST/check-markit/FVT-setup.sh
/usr/local/bin/git-TEST-cases.sh: line 292: cd: ./TEST/FVT-setup.sh
./hooks/EXAMPLES/TEST/FVT-setup.sh: No such file or directory
Expected results:
A clear and concise description of what results you expected.
Tell us about your incident:
A clear and concise description, 'what is your incident?'
-> add a prompt or user help when there are more then one --filename in the repository
To reproduce your incident:
Steps to reproduce your incident:
Actual results:
If applicable, add screenshots to help explain your incident.
Expected results:
A clear and concise description of what results you expected.
Command: ( check-markit 4.1.4.803 2020-08-29T22:25:47.061044-05:00 (CDT) https://github.com/BradleyA/markit.git master uadmin )