Great vid and well explained, thanks. Here's a small tip I found the other day: At 7:12 where you push to the branch you're on, an easier method is "git push -u origin HEAD". This always pushes to the current branch, which is really useful for feature branches that have long names (they often include some kind of tag such as FEATURE, a ticket ID, and a description).
I dont code for crap. Doing solo development for UE4 and well blueprints is a godsend. This is helping a lot and I thank you for it. I been browsing, watching a ton of videos and your seem to really help me understand. I am kinda slow at learning/understanding but still worth the wait. Thank you.
Hey CJ, I have a question in 9:56, you mention that you do squashing commit, how do you do that? Is that responsibility for the maintainer to squash commits if any pull request contains multiple commits? or is it contributor responsibility to make sure squash the commit before create a pull request?
Yeah GitHub has the option to squash commits before merging. I have been on some teams that require the contributor to squash commits before making a pull request though. It is usually not the maintainers responsibility.
In this video I'm using bash with a custom prompt that uses the command vcprompt to show the current branch. The easiest way to get this yourself is to use ohmyzsh, ohmybash or ohmyposh to get shell customization (including git info) out of the box.
Alternatively, as a workaround that's free, the Trello card ID suffices, e.g. for a card with URL `trello.com/c/abcDEF12/my-new-feature`, you might call your branch `feature-abcDEF12`.
Great vid and well explained, thanks. Here's a small tip I found the other day: At 7:12 where you push to the branch you're on, an easier method is "git push -u origin HEAD". This always pushes to the current branch, which is really useful for feature branches that have long names (they often include some kind of tag such as FEATURE, a ticket ID, and a description).
I dont code for crap.
Doing solo development for UE4 and well blueprints is a godsend.
This is helping a lot and I thank you for it. I been browsing, watching a ton of videos and your seem to really help me understand. I am kinda slow at learning/understanding but still worth the wait.
Thank you.
Thanks for this tutorial CJ. Improved my understanding of the git workflow
These videos are very helpful. thank you
Thanks man, amazing in depth explaining..........!
Hey CJ, I have a question in 9:56, you mention that you do squashing commit, how do you do that? Is that responsibility for the maintainer to squash commits if any pull request contains multiple commits? or is it contributor responsibility to make sure squash the commit before create a pull request?
NVM, I just found there is another option to merge a pull request by squashing the commit.
Yeah GitHub has the option to squash commits before merging. I have been on some teams that require the contributor to squash commits before making a pull request though. It is usually not the maintainers responsibility.
What is gss and gcs command?
This was a great example, it really helps me to understand the flow. Thanks 🤘🏼
Another great video man. I have a question: What is the tool you use for showing branches? That minima thing?
In this video I'm using bash with a custom prompt that uses the command vcprompt to show the current branch.
The easiest way to get this yourself is to use ohmyzsh, ohmybash or ohmyposh to get shell customization (including git info) out of the box.
Crazy helpful! thankyou so much
this was so helpful.. thanks a lot man!
how can i add so i see the current branch on my own terminal?
Poze i use zsh and oh-my-zsh to accomplish that. most themes have that feature
How do you get card numbers on trello?
We are using a power up: trello.com/power-ups/59c3d177178a761767b49278/card-numbers-by-reenhanced
Alternatively, as a workaround that's free, the Trello card ID suffices, e.g. for a card with URL `trello.com/c/abcDEF12/my-new-feature`, you might call your branch `feature-abcDEF12`.