Egit files pushed to master don't show on github, but appear in clone of repo - push

Using Egit 3.0, I did a "Pull" to get latest master from github. Merged local changes into master and committed. Then did a "Push To Upstream." During the push I got a timeout warning. I could not see my commit or changed files when browsing github so I tried push again - message "Master: master up to date." Tried pull again - message "No ref to fetch from origin - everything up to date." Still not seeing changes or commit on github. Went to another machine and did a pull from master. All of the changes and new files are in that pull! I then did a new clone of the master. All the changes are in that as well. Any idea why the files are not showing up on the github site and how to get them to appear?

Github the cleared cache and fixed the problem!
I contacted support at github.com on this issue and they responding saying that they "cleared the cache." Now I can see my new and changed files on the github site. It's is more often the case that user error is responsible for issues like this, but this time it seems it was something that support needed to do.

Related

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.

How to commit code changes from Eclipse to GitHub

I tried committing the entire project folder to my Github repository:
https://github.com/rahul-raj/SpringBoot
However when I try "Commit and Push", I get "master rejected non fast forward" error:
I tried pull/fetch, but it doesn't work either, getting "nothing to fetch" error:
When I try to commit and push the projects, now it says "0 Changes to be committed", but there are no such projects uploaded to my Github repository.
Can someone tell me how to fix this and push the project to my Github?
I was looking into several related Stack Overflow posts and nothing fixes my issue. How can I fix this through STS/EFclipse itself?
Probably your local history differs from the already existing remote history (e. g. caused by an amend commit to an already pushed commit).
In this case, in the Push Branch dialog you have to select the option Force overwrite branch in remote if it exists and has diverged. Maybe you need to allow force push in your GitHub repository first.

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!

Github not checking if local repo has changed

I recently re-installed my computer,
and now I'm encountering problems with github for windows (I'll be using GFW in the rest of this text). it say's that my local repo is in sync, but even if I change things, delete files, or add files it keeps saying that it is in sync.
It does check if I make changes on a different computer and push them. but syncing then won't work, so I went to shell
there I can commit (shows in GFW that there are commits ready to be pushed), sync button in GFW still doesn't work (showing that there are problems, and I should continue in git shell). When I commit in shell says that there are changes , insertions, and deletions
Then when I want to push it says Everything up-to-date.
Anyone got any clue what is going wrong?
Check if you are actually on a branch: are your commits made on a branch, or on a "detached HEAD"? (more on this at "cannot push to GitHub: everything up-to-date").
A simple git branch can show you the active branch. If there are none, that would explain why the "sync" button is inactive. You need to fast-forward your branch to that detached HEAD.

eclipse and github: master: master rejected?

I'm working with a friend using github and eclipse. Initially he created the repository and pushed his code. The only way I'm able to push my changes are to "force" them but this unfortunately wipes out his data and replaces it with mine. If I uncheck the force option I see the following error when trying to push my changes:
master: master [rejected]
Do I need to start over and pull the source from the repository initially?
Before pushing your changes, you will need to merge his changes locally. Try:
git fetch
git merge origin/master
After you have performed this merge and resolved any conflicts, you should be able to push your changes back up to Github.
The reason your change is rejected is that the current master on Github does not appear anywhere in the history of your master branch.