GitHub Desktop Stuck on Pushing To Origin - github

When I tried to push to remote repository using GitHub Desktop Application, it stuck on Pushing to origin.
How to solve this? I tried reinstall but that does not fix the issue.

check if you have saved all the changes that you made recently or not.
for that type git add. (Dot is mandatory)
after adding commit the changes git commit
now all changes have came to staging area, now you can push the files..
Hope it helps you...
correct me if i am wrong.

Related

Losing changs during github stages, commit and push to the repository

Iam using git and github with vscode,
I stashed changes , committed them and pushed them into my repository, using push to.
All the steps had done without any git command in terminal,
My problem is all my changs have not showing on the repository and my new changs had deleted from vscode.
Why this happening?
can i restore my changs into vscode?
I make the same steps everytime and i never faced this problem,
Could any one explain what happened and helps me.
Thanks in advance.

Pushing changes to a github repo without having to pull

So I've recently started using github and made my own repo and pushed a project there. I understand that to fix the error saying "Remote repository contains unmerged into the local branch", you must pull or fetch.
The problem is that I made some major changes (remade file hiearchy, removed some files and added some as well) and now I do not want to pull since it would add back the files I removed and now, whenever I push, the error mentioned above pops up. How do I push the changes I made then?
You can force push the changes you have made
git push --force origin branch_name
Seems like Git stash is what you need here.
If you have made some changes then that will automatically get applied on top of the remote changes. So if you take a pull, still you will see your changes on top.

Removing a file completely from Github Classroom

I have followed this way to remove a file permanently from my GitHub Repo
https://help.github.com/articles/removing-sensitive-data-from-a-repository/
However I am not sure If this also works with the Github Classroom ? I have pushed a file accidentally that I do not want anyone to see. Is this a Safeway to make sure the file is deleted 100% and no other contributor has access to it ? Is this going to appear as a new commit ?Assuming that my professor has not cloned it yet.
Thanks
If you can do the step 6 (git push origin --force of your branch you have cleaned up), that should be OK.
But that supposes nobody cloned that branch (as you mention).
And it supposes that a force push was not disabled on the remote side (as it was in issue 458)

What should I do when my local branch is at merging state after I pull the remote master?

I am an Android developer, and now I am doing a lot of changes locally and are trying to synchronize the local and github side of the code after I pull the merge to merge successfully and merge the code locally and run successfully.
But when I want to push always show the picture shown in the picture, push rejected. I am very puzzled, the left side of the figure is the local change, since I was a novice, no previous to ignore the file, so a series of build files, .idea files have been submitted to see the error is to show that these files are not merged.
Now I am very puzzled, how can I solve this situation, how can I submit the local code to my github library, who can help me? Many thanks!
Screenshot:
You have commits in the remote version of master that you're pushing to that are not in your local version, and vice versa. Since Git can't resolve this diversion automatically, you can't push your local version to your remote.
You may have to git pull, or if that doesn't work, git rebase, to get your branches to line up in a way that they can be merged.

GitHub - no changes seen after successful commit

I'm struggling with an issue connected to GitHub. I've committed some changes using GitBash console and got an info that the push was successful and there's nothing to commit. When I went into logs, there was this particular log looking like this:
The issue is that when I go back into my GitHub account, I can see just an initial commit in there, nothing more.
And the console clearly says that the commit was successful.
Please help!
Git is a distributed version control system, so you have one local copy of the repository, Github has another copy. As far as git is concerned every copy is equally important.
For your changes to exist in Github, you have to push them there, with something like:
git push origin master
Try git remote -v to get more information on your tracked repositories. Github has some great help pages on this stuff.
For what you say in your question, I think you don't have actually pulled your local repository in your GitHub account.
To do that, use git push origin master
When you use git commit your changes are saved in your local repository, not in your remote (that in this case is GitHub)
Thanks to all that helped me understand my issue. Turns out the files did not copy between folders properly and that's why there're not changes detected on git. Now everything is working.
Thanks again!