Git
Error encountered while pushing to the remote repository: Git failed with a fatal error. unable to access 'https://github.com/Ginger-Automation/Ginger/': Could not resolve proxy:
git config --global http.proxy MyHTTPPROXYURL
Where MyHTTPPROXYURL is thr proxy URL
i.e.:
git config --global http.proxy http://genproxy:8080
Reset git proxy
git config --global --unset http.proxy
Tips for creating good commit messages The commit message content is more important that it may seem at first sight. Git allows to add any kind of explanation for any change we made, without touching the source code, and we should always take advantage of this. For the message formatting, there’s an unwritten rule known as the50/72rule, which is so simple: • One first line with a summary of no more than 50 characters. • Wrap the subsequent explanations in lines of no more than 72 characters. This is based on how Git formats the output when we are reviewing the history. But,more important than this, is thec ontent of the message itself. The first thing that comes to mind to write are the changes that have been made, which is not bad at all. But the commit object itself is a description of the changes that have been made in the source code. To make the commit messages useful,you should always include the reason that motivated the changes.
Add extension to VS https://services.github.com/on-demand/windows/visual-studio
Spice it Up!