Outputting if the last command was a successful git checkout
I am trying to echo to the console in the event that a successful git checkout happened, but cannot get it to work.
function prompt_command {
prev=`fc -ln -1`
ecode=$?
if [ ecode = 0 ]
then
if [ `echo $prev | grep -c "^git co -b"` -ge 0 ] || [ echo $prev | `grep -c "^git checkout -b"` -ge 0 ]
then
echo "SUCCESSFULLY CHECKED OUT!"
fi
fi
}
export PROMPT_COMMAND=prompt_command
Context:
The eventual aim is to update the new git branch's description to indicate which branch it was checked out from. E.g. If I checkout "my_new_feature" from "dev", I want to automatically run:
git config branch.my_new_feature.description "[FROM:dev]"
Then modify the prompt to include the parent branch.
bash git
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
asked Dec 17 at 23:30
paul dilley
61
add a comment |
I am trying to echo to the console in the event that a successful git checkout happened, but cannot get it to work.
function prompt_command {
prev=`fc -ln -1`
ecode=$?
if [ ecode = 0 ]
then
if [ `echo $prev | grep -c "^git co -b"` -ge 0 ] || [ echo $prev | `grep -c "^git checkout -b"` -ge 0 ]
then
echo "SUCCESSFULLY CHECKED OUT!"
fi
fi
}
export PROMPT_COMMAND=prompt_command
Context:
The eventual aim is to update the new git branch's description to indicate which branch it was checked out from. E.g. If I checkout "my_new_feature" from "dev", I want to automatically run:
git config branch.my_new_feature.description "[FROM:dev]"
Then modify the prompt to include the parent branch.
bash git
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
asked Dec 17 at 23:30
paul dilley
61
[ ecode = 0 ]should be[[ $ecode -eq 0 ]]
– l0b0
Dec 17 at 23:46
Or[ "$ecode" = 0 ].
– G-Man
Dec 17 at 23:47
add a comment |
I am trying to echo to the console in the event that a successful git checkout happened, but cannot get it to work.
function prompt_command {
prev=`fc -ln -1`
ecode=$?
if [ ecode = 0 ]
then
if [ `echo $prev | grep -c "^git co -b"` -ge 0 ] || [ echo $prev | `grep -c "^git checkout -b"` -ge 0 ]
then
echo "SUCCESSFULLY CHECKED OUT!"
fi
fi
}
export PROMPT_COMMAND=prompt_command
Context:
The eventual aim is to update the new git branch's description to indicate which branch it was checked out from. E.g. If I checkout "my_new_feature" from "dev", I want to automatically run:
git config branch.my_new_feature.description "[FROM:dev]"
Then modify the prompt to include the parent branch.
bash git
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
asked Dec 17 at 23:30
paul dilley
61
I am trying to echo to the console in the event that a successful git checkout happened, but cannot get it to work.
function prompt_command {
prev=`fc -ln -1`
ecode=$?
if [ ecode = 0 ]
then
if [ `echo $prev | grep -c "^git co -b"` -ge 0 ] || [ echo $prev | `grep -c "^git checkout -b"` -ge 0 ]
then
echo "SUCCESSFULLY CHECKED OUT!"
fi
fi
}
export PROMPT_COMMAND=prompt_command
Context:
The eventual aim is to update the new git branch's description to indicate which branch it was checked out from. E.g. If I checkout "my_new_feature" from "dev", I want to automatically run:
git config branch.my_new_feature.description "[FROM:dev]"
Then modify the prompt to include the parent branch.
bash git
bash git
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
asked Dec 17 at 23:30
paul dilley
61
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
asked Dec 17 at 23:30
paul dilley
61
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
edited Dec 17 at 23:36
Rui F Ribeiro
39k1479129
39k1479129
asked Dec 17 at 23:30
paul dilley
61
asked Dec 17 at 23:30
paul dilley
61
asked Dec 17 at 23:30
paul dilley
61
61
[ ecode = 0 ]should be[[ $ecode -eq 0 ]]
– l0b0
Dec 17 at 23:46
Or[ "$ecode" = 0 ].
– G-Man
Dec 17 at 23:47
add a comment |
[ ecode = 0 ]should be[[ $ecode -eq 0 ]]
– l0b0
Dec 17 at 23:46
Or[ "$ecode" = 0 ].
– G-Man
Dec 17 at 23:47
[ ecode = 0 ] should be [[ $ecode -eq 0 ]]– l0b0
Dec 17 at 23:46
[ ecode = 0 ] should be [[ $ecode -eq 0 ]]– l0b0
Dec 17 at 23:46
Or
[ "$ecode" = 0 ].– G-Man
Dec 17 at 23:47
Or
[ "$ecode" = 0 ].– G-Man
Dec 17 at 23:47
add a comment |
1 Answer
1
active
oldest
votes
[ ecode = 0 ] should be [[ "$ecode" -eq 0 ]]:
- Double brackets
- Use More Quotes™
- Use a dollar sign in front of variables to expand them (
[[is a special case where you don't strictly need dollar signs or quotes in this case) - Use
-eqfor integer comparison
answered Dec 17 at 23:48
l0b0
27.6k17113242
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489586%2foutputting-if-the-last-command-was-a-successful-git-checkout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
[ ecode = 0 ] should be [[ "$ecode" -eq 0 ]]:
- Double brackets
- Use More Quotes™
- Use a dollar sign in front of variables to expand them (
[[is a special case where you don't strictly need dollar signs or quotes in this case) - Use
-eqfor integer comparison
answered Dec 17 at 23:48
l0b0
27.6k17113242
add a comment |
[ ecode = 0 ] should be [[ "$ecode" -eq 0 ]]:
- Double brackets
- Use More Quotes™
- Use a dollar sign in front of variables to expand them (
[[is a special case where you don't strictly need dollar signs or quotes in this case) - Use
-eqfor integer comparison
answered Dec 17 at 23:48
l0b0
27.6k17113242
add a comment |
[ ecode = 0 ] should be [[ "$ecode" -eq 0 ]]:
- Double brackets
- Use More Quotes™
- Use a dollar sign in front of variables to expand them (
[[is a special case where you don't strictly need dollar signs or quotes in this case) - Use
-eqfor integer comparison
answered Dec 17 at 23:48
l0b0
27.6k17113242
[ ecode = 0 ] should be [[ "$ecode" -eq 0 ]]:
- Double brackets
- Use More Quotes™
- Use a dollar sign in front of variables to expand them (
[[is a special case where you don't strictly need dollar signs or quotes in this case) - Use
-eqfor integer comparison
answered Dec 17 at 23:48
l0b0
27.6k17113242
answered Dec 17 at 23:48
l0b0
27.6k17113242
answered Dec 17 at 23:48
l0b0
27.6k17113242
answered Dec 17 at 23:48
l0b0
27.6k17113242
27.6k17113242
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489586%2foutputting-if-the-last-command-was-a-successful-git-checkout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
[ ecode = 0 ]should be[[ $ecode -eq 0 ]]– l0b0
Dec 17 at 23:46
Or
[ "$ecode" = 0 ].– G-Man
Dec 17 at 23:47