what is difference of gitlab project activitiy time stamp and commit time stamp? - push

When I commit the source , commit time is changed(first picture)
but project activity history changed nothing!(second picture)
Why is commit time not reflected on project activity?

Related

How to restore commit history before first release on Github

I have a repository where I made many commits in January. Fast forward to July, when I was tinkering with Git, I got to know about the Releases feature.
Since I had many major features to push, I decided to create a new release.
Now I need the January commits for showing to someone but there is no trace of them anywhere, neither in the Commits section nor in releases. It just shows 4 commits since this release
The commit history shows as if I started commiting to the repo from July only
Any help is appreciated.
Somehow, my entire history was stored not in branch but in a tag that I created when creating that release.
That's why even going too much deeper didn't reveal anythin since the commits were HEADless.
I noted the tag's hash and did
git checkout tag-hash // now no branch checked out
git checkout -b new-branch-name tag-hash // created new branch from that tag
And with this, my new branch has the whole commit history

Push/Commits in VS Code not showing in GitHub Calendar

I have made a repo through VS Code and have been pushing updated through VSC itself. The commits can be seen in the commit history of the repo but for some reason the Calendar and Activity is not updating and in my profile.
This shows that my push from VSC is present in GitHub
But there is no update in the activity or calendar

github files not the same as latest commit?

I am having trouble understanding/ updating one of my git repos. There is one branch, master. I created the repo on github. Cloned and made edits in Windows, commited, pushed. Cloned in Mac, made edits, committed, and pushed. A few days later made commits from Windows again. Now Github shows my latest commit different code than the files do. Shouldn't github files be synced to the latest commit?
On my Windows machine the repo matches the commit changes shown in the latest commit. (The commit hash link in upper right of github.)
This is different from the repo and on my Mac, which matches the Raw file.
Why does the commit hash show a file with changes, while clicking the file link show the file before the changes? (seems to be root of problem)
How can the files be different than the most current commit?
The repo in question:
The file:
https://github.com/dval/HWiNFO64-Crunch/blob/master/HWiNFO64%20parsing.R
The hash:
https://github.com/dval/HWiNFO64-Crunch/commit/57c44c441ee0d2b39fa5248eaf44b10a3658a023

Commit history of projects prior to its date of creation on GitHub

What does it mean when base repositories of projects hosted on GitHub have commit history prior to project creation date on GitHub? Also, what does it mean when forks of a project have commit history prior to its creation date on GitHub?
It simply means that the user that created that repository managed the repo before, outside of GitHub.
Imagine this as a document in Dropbox, you create it today in your computer, you upload it next week to Dropbox:
Date of creation: 27th Jan 2015
Data of file creation on Dropbox: 4th Feb 2015
This might seem tricky to you because you, if youare not distinguishing git and github. You can have a whole network of git repositories without GitHub.
GitHub provides visualization and great tooling on top of git repos.

GitHub synchronize failure result in rebase - how to get back the committed file

I've made a commit to GitHub but the synchronization was not successful and it abort half way. When I try to get back the files I realized the files in local has been rebased to the previous version that I submitted during the last synchronization.
The new files and editions were lost. May I know whether there's any way to get back the lost data?(now it says "Rebase origin/master **" on my project)
Thank you!
Use the following:
git log
copy any previous commit id.
git reset "commitid".
Now you will have your changes.
Then commit and rebase.