Description
ISSUE: from a script
Log:
...
(mvn build)
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.419 s
[INFO] Finished at: 2019-10-08T16:33:35+02:00
[INFO] ------------------------------------------------------------------------
[master 8269297] Release v5.16.3
5 files changed, 5 insertions(+), 5 deletions(-)
warning: failed to restrict file handles (5)
handle #0: 0000000000000440 (type 3, handle info (1) 0
handle #1: 0000000000000444 (type 3, handle info (1) 1
This is a bug; please report it at
https://github.com/git-for-windows/git/issues/new
To suppress this warning, please set the environment variable
SUPPRESS_HANDLE_INHERITANCE_WARNING=1
Already up to date.
...
Setup
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
git version 2.23.0.windows.1
cpu: x86_64
built from commit: 4db2e5c
sizeof-long: 4
sizeof-size_t: 8
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
Microsoft Windows [Version 10.0.18362.356]
- What options did you set as part of the installation? Or did you choose the
defaults?
Editor Option: Notepad++
Custom Editor Path:
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: OpenSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Performance Tweaks FSCache: Enabled
Use Credential Manager: Disabled
Enable Symlinks: Disabled
Enable Builtin Interactive Add: Disabled
- Any other interesting things about your environment that might be related
to the issue you're seeing?
Command window was started from inside SourceTree (Clicked on Terminal)
Details
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
MingW64?
- What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
I ran a script.
This were the last commands of that script:
********** START **************
git merge develop
mvn org.codehaus.mojo:versions-maven-plugin:set -DnewVersion=${NEW_VERSION} versions:commit
find . -name 'pom.xml' | xargs git add
git commit -m "Release v${NEW_VERSION}"
git pull
git push
*********** END ***************
So it seems that it appeared at the end of the commit, or at the start of the pull
- What did you expect to occur after running these commands?
** insert here **
- What actually happened instead?
everything seems to be allright?!?
- If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
no