Here’s a really quick video on the merge completion, including the merge commit message, deleting the branch and push-pull operation. View file changes from the Pull Requestįinally, when all the review work is done and it is time to merge the branch, you have the same three options that you get on. Selecting “View file changes” will open the diff view of a file between branches. For example, you’ll see the expected features that are important in the context of a Pull RequestĬlicking “Review Changes” allows you to comment, approve and request changes. GitKraken doesn’t want to move you cheese, it wants you to be more efficient. Go ahead and select one to load it into GitKraken’s main viewport.Īt this point, the UI might look familiar because the layout is intentionally similar to GitHub’s layout of a Pull Request. If you expand it, you’ll find a list of open items with their PR number. You can see any pending Pull Requests in the left column, specifically you’ll see a number next to the PULL REQUESTS section header. If you don’t have GitKraken yet, you can get it using my personal invite link. For more in-depth information, please visit this official documentation. In today’s post, I’m going to show the high level set of features inside of GitKraken that let you achieve the basic set of operations that are needed when you’re reviewing and approve a Pull Request. This is why I love the new support for GitHub Pull Requests in GitKraken. It is a win for everyone when you can consolidate multiple tasks into a single workspace and workflow. Double-check your assignment group within your tutorial has not changed, i.e. Note: Some tutorial groups may have undergone some slight last-minute modifications. One of the hallmarks of a professional workspace is an efficient workflow with powerful tools. This tutorial is under construction, so some questions might change / be added before the tutorial.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |