Has anyone recovered a Bitbucket Mercurial Repo that was deactivated in 2020? - version-control

Bitbucket Mercurial support ended on July 1, 2020. My repos were deactivated at that time. Has anyone recovered their deactivated Mercurial repos, and how was that accomplished?

This is the archive of all public Mercurial projects that were hosted on Bitbucket before they removed Mercurial support on July 1, 2020.
Some projects might be unavailable or incomplete because they were deleted or made private before we had a chance to archive them.

Related

Whats the easiest and noob friendly way to move changes from github to tfs?

I have a project hosted on TFS, let's call it GenderBlender. Two teams work on GenderBlender. One team got the latest code from TFS and hosted it on Github. Made some commits to that GitHub. How can I move those changes from Github to Tfs without commit history and just one big commit under my account?
I will be moving it from my local git repository to my local tfs repository and then committing them to the tfs.
That is actually the idea: copy the all files from the Git repo to the tfs working tree (be it a TFVC workspace or a Git one)
If it is a Git repo, Git will detect the changes: add and commit.
If it is a TFVC workspace, use a reconcile command to detect the changes

Dockerhub Automatic Build with Github LFS

I want to introduce Git LFS in my github repository.
Does dockerhub automatic builds support Git LFS?
What happens if dockerhub Automatic Build checks out a Git LFS repository?
There is nothing regarding lfs in docker/hub-feedback.
Nor is there anything in docker/notary or docker/docs.docker.com, or docker/distribution
The Docker Hub Automatic build "allow[s] you to use Docker Hub’s build clusters to automatically create images from a GitHub or Bitbucket repository containing a Dockerfile".
Since Git LFS is only official on GitHub repos is only official for the last 14 days, and being worked on for BitBucket (coming from their original Git LOB initiative), it seems safe to say LFS isn't yet supported by an Automatic build.
Update June 2016, Andy Li reports in the comments below:
There is now a feature request issue in docker/hub-feedback:
Issue 500: "Add support for Git LFS".
It needs your support (or your Pull-Requests)
4 years later, Q4 2019, you might consider as an alternative GitHub Actions. Check this other question for more details on how to use git-lfs in them.

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.

Forked a SVN project to GitHub, project now moved to GitHub. Possible to merge?

I forked a SVN project on GitHub some 2 months ago, using git-svn (git svn rebase), and made my changes, sending some (but not all) via patch files back.
Now the project moved to GitHub, is there any way I can merge these two GitHub projects while keeping my fork's history?
If the import has been done properly, the SHA1 for the content imported on GutHub from SVN should be the same than the SHA1 generated by your git-svn fork on GitHub.
If that is the case, then "Merging between forks in GitHub" is your answer (or "Merge changes from remote GitHub repository to your local repository").
If not, it is best to recreate your fork from the official GitHub repo, and re-apply your work as patches on top of said new fork.

Github for Windows sync issue

As of the latest version of Github for Windows (1.0.24), I began having issues merging and syncing repos. I have an enterprise github account.
Here is an example situation, I merge my develop branch into the master, but the commit does not display when viewing the master branch in GFW. Therefore the sync option is not available because GFW believes the code on the local repo and server are in sync.
When I look at the master branch source code, I see the the latest commits from the develop branch that were merged into it are there. GFW does not display any commits EXCEPT when you use the Manage branch option. There you can see the lastest commit is the in the master branch.
Something is out of whack, maybe its me!
Any thoughts?
Yep, I get the exact same thing from time to time - you're not crazy.
I wish they'd fix it though