How to push changes to Git Hub using GIT GUI?

 

  1. Right-click the "Remotes" section header in the sidebar and select "Add Remote Repository"
  2. In the dialog, you can enter a name (e.g. "origin") and the remote repo's URL on Github; additionally, you can select your GitHub account
  3. Confirm the dialog and the remote will now be connected with your local repository
  4. From now on, you can simply use the "Push" button in the toolbar to upload new changes to the remote on GitHub

Comments

Post a Comment

Popular posts from this blog

What is a client and a server?

  According to  a client-server architecture, clients request services from a server. Servers provide the requested service to their clients. However, clients and servers are separate programs running on different machines.  Clients act as the front end, and servers remain at the back end. Clients are in charge of delivering the user with data, whereas servers are in charge of storing and managing the data. The definition of a Client is as below:- A computer device that asks a server for services is known as a customer. The customer is the front-end element in client and server architecture which communicates with the user and sends requests to the server. Some examples are  laptops, desktops, etc. The definition of  a Server is as below:- A server offers services to other devices connected to a network. A server's primary functions include accepting and completing customer requests as well as storing and managing data. Some examples are  web servers, datab...
Read more

Why is it important to have a detailed bug description with evidence?

An effective bug report should contain the following: Title/Bug ID Environment Steps to Reproduce a Bug Expected Result Actual Result Visual Proof (screenshots, videos, text) of Bug Severity/Priority  Title/Bug ID:  The title should provide a quick description of the bug. For example, “ Distorted Text in FAQ section on <name> homepage ”. Assigning an ID to the bug also helps to make identification easier. Environment: Device Type : Hardware and specific device model. OS: OS name and version. Tester: Name of the tester who identified the bug. Software Version: The version of the software which is being tested, and in which the bug has appeared. Connection strength:If the bug is dependent on the internet connection (4G, 3G, WiFi, Ethernet) mention its strength at the time of testing. Rate of reproduction:The number of times the bug has been reproduced, with the exact steps involved in each reproduction.  Steps to Reproduce a Bug:  Number the steps clear...
Read more