gitHub Desktop view Executed Command - github

Is it possible to view the commands executed by github desktop when I use it to commit, push, etc. ?
I am fairly knowledgeable about git, but pushing to github.com and a master by command line could use some work.
So, I am using GitHub desktop to commit back to github.com and would like to see the actual commands that the GitHub desktop app uses when I push the "publish repository" button... and others.
Github Desktop for Mac if it makes a difference.

Check first the logs, as seen in desktop/desktop issue 7690
To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs in Finder (macOS) or Explorer (Windows).
The log files are created daily
desktop/desktop issue 8516 made a similar request, but the answer was:
This is an interesting idea, but but not something that we will likely tackle in the near-term. I'm going to label this issue as an enhancement and close it out -- if we get further feedback that this would be a valuable addition to GitHub Desktop it may be something we consider in the future.
If you are interested in viewing the specific actions that GitHub Desktop is performing you can open up the Developer Tools by going to the menu and selecting View > Toggle Developer Tools and selecting the Console tab.
You will see the the specific Git commands that are being run, along with other output.
For the most verbose output you can click the All levels dropdown and select Verbose. The log files also provide a historical view of this data, and you can access those by going to Help > Show Logs.... If you have any specific questions about the commands that are being run let me know.

Related

How to open your own github repo from github.dev

In the new product of Microsoft, github.dev, you are automatically forwarded to a VSCode web IDE. However, I am not sure if it is possible to open your own repo (hosted on github.com), work on it and push the changes. Can you help explain if this can be done and how?
I do not seem to find a straightforward tutorial on that.
Note that I was able to open a repo of mine by clicking on the blue GitHub icon in the bottom left corner, but I fail to install a terminal, because
Terminals are not available for web editor. To use terminal you need to continue working in an environment that can run code, like codespaces or local VS Code
I read that codespaces are a paid option for github enterprise, but the way this error message is written might suggest other ways.
Opening your repository
You can open your repository by visiting it's page on GitHub and pressing . to open it in github.dev. You can also use the url format https://github.dev/<username>/<repo-name> with the path to your repository.
Making Commits
While the terminal cannot be used in the editor, you can make commits using the VSCode source control system.

Removing Sensitive Data From Github using GUI?

I accidentally uploaded a bunch of very sensitive client projects to Github. I need to remove them immediately.
I'm very new to Git. I don't know how to use the terminal. I'm using Github Desktop on Mac. Can someone please explain it to me in the simplest terms possible how to quickly and effectively purge/remove full directories from a GitHub repository's history without using terminal? (or very very simple specific instructions on how to use terminal to do this?)
I found some terminal directions already through Google, but I don't know how to use it. I can't find any option on github.com to do it via browser, and the Desktop app doesn't seem to allow history of files or directories.

Connection to Github from VS code fails

I am trying to connect VS code (on win10 machine) to github.
The GitHub Pull Requests and Issues is installed and enabled.
I followed few YouTube guides in which it was mentioned the git button that should appear on the upper right side of the explorer window, in order to add the project to the source control section.
This button doesn't appear at all.
Any idea?
Thank you
Since I post this message, VScode released a new version which makes the connection to Github very simple. For newbies like me that need to establish the connection, you may use the process I use:
1- Create a repository on github, and copy the link to the repo
2- In VScode, in view, command palette: GitClone, then add the link you just copied, select the folder where you want to store the repo on your local drive, and that's it.
3- Use the Source Control button on right, and them stage your changes, commit - and now only push/pull or sync.
Good luck.

How do I commit to a remote repository on Visual Studio?

I figure this may be somewhat of a common question, but I am still having trouble with what I am finding. Note: I am very new to deploying applications. I have created my first application, an ASP.NET MVC application using Visual Studio Community 2015(I am using enitity framework for the database if that matters). It is time for me to deploy it. I have all my files on gitHub. Now I believe it is time for me to commit to my remote repository on AppHarbor (which I have the link for), but I just can't seem where to do it. It seems to be so simple. I'm using the team explorer. Again, I am very new to programming and deploying applications, so any help would be amazing. Again, from what I understand I need to connect to my remote repository now. I could be wrong. Thank you very much for any insight.
Inside Visual Studio, open the 'Team Explorer - Connect' Window. Default Shortcut for that should be Ctrl+/ + Ctrl+M.
Inside the Team Explorer window, Click on the green plug like button that you see that says "Manage Connections". You will be able to connect to your remote repo from here.
After that, Click on 'Clone' and paste your repo's URL in the yellow text box:
If your remote repo is on the GitHub, this is where you can find the URL to your remote repo:
Well, that's it.. you're connected! To commit your changes, you can easily find the "Changes" section in 'Team Explorer' window. Here's a screenshot for that too:
Note that in my case some of the buttons shown may be Disabled. That should not be a problem to you if you have files with changes, etc.
I don't know about Visual Studio, but with git you need to push your changes to a remote repo, so maybe you have a "push" somewhere ?
First you need to add this remote repository.

GitHub for Windows is showing old README text

There is a panel on the right that is supposed to show current content of README.MD. However, I noticed that after changing the content of REAMDE.MD is hasn't updated the text in the panel. Is there a way to forcefully refresh it?
The version of GitHub for Windows I have is 1.0.41.2 (fd3fd236ac85e622194e88f248576b9fe25d28d4)
Yeah, sorry about that. It's a bug and we're working on it. It's currently cached for 30 minutes and sometimes it doesn't expire when it should.
The only way to force a refresh currently is to either delete the entire folder at %LocalAppData%\GitHub\BlobCache.api.github.com or to locate the file in that folder that holds the README content (by looking for keywords that would appear in the README for example) and deleting that.
After a quick search in the \AppData\Local\GitHub folder I found that the old value from README.MD is stored in one of the files in the BlobCache.api.github.com. Deleting the whole folder and restarting the app solved the issue.
Still wondering if there is a proper way for doing that from UI? Shouldn't it happen automatically anyway?
This came from GitHub staff. It tells you how to clear the cache.
WARNING: This will remove GH4W's references to your local repositories
and your logged-in account. You will have to log in again and let GH4W
re-scan your computer for repositories.
There's a known bug where we cache the 'NO README' view if you add a README after adding the repository to GitHub for Windows.
If you'd like to try to get the README to show up, you can delete the cache:
Here are the steps you will need to follow to delete the cache:
Close GitHub for Windows
Open the Git Shell
Run 'github —delete-cache' to clear our the GitHub for Windows cache
Restart GitHub for Windows — you will need to log in and add your repositories again