For my link archive: [Wayback] version control – Migrate from bitbucket to GitLab – Stack Overflow
Documentation: [Wayback] Import your project from Bitbucket Cloud to GitLab | GitLab
–jeroen
Archive for the ‘BitBucket’ Category
version control – Migrate from bitbucket to GitLab – Stack Overflow
Posted by jpluimers on 2022/05/24
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitLab, Software Development, Source Code Management | Leave a Comment »
Bitbucket: diffing a file between two commits in a git repository
Posted by jpluimers on 2020/08/27
Example URL to diff Spring.pas over two commits in a git repository (reminder to self: see if I can find similar information for a Mercurial repository):
This diffs the file https://bitbucket.org/sglienke/spring4d/src/master/Source/Base/Spring.pas over these commits
- https://bitbucket.org/sglienke/spring4d/commits/ca8037a2fdecbdbb23d3b997d1160f72838cee02 (a
masterbranch release of version1.2.1) - https://bitbucket.org/sglienke/spring4d/commits/8f4d03020613 (a commit I was historically interested in to update a really old project)
–jeroen
Share this:
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
Sunsetting Mercurial support in Bitbucket – Bitbucket
Posted by jpluimers on 2020/01/30
February 1st, the start commences of Sunsetting Mercurial support in Bitbucket – Bitbucket [WayBack]. Starting June 1st, only git is supported by Bitbucket, despite them having started with and focused mainly Mercurial at first.
Here are the major dates of the sunset:
- February 1, 2020: users will no longer be able to create new Mercurial repositories
- June 1, 2020: users will not be able to use Mercurial features in Bitbucket or via its API and all Mercurial repositories will be removed.
All current Mercurial functionality in Bitbucket will be available through May 31, 2020.
So by now you should have started migrating from Mercurial to git, probably away from BitBucket.
Share this:
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Software Development, Source Code Management | Leave a Comment »
git on Windows: prevent “The requested URL returned error: 403” during push of https based repository
Posted by jpluimers on 2019/01/10
When you search for git push "The requested URL returned error: 403", then the usual answer is “use ssh over https”, for instance at [WayBack] github – Pushing to Git returning Error Code 403 fatal: HTTP request failed – Stack Overflow.
However, lots of places (especially larger corporations and financials) limit outgoing traffic to http and https based for (often perceived) security reasons.
In this case, I needed a solution for Windows, which – after a long search – found two solutions that are below.
I use the https://gitlab.com/wiert.me/examples/sql-examples.git repository as an example, but it isn’t limited to GitLab: the same symptoms happen with other hosters as well (for instance on GitHub and BitBucket):
First what doesn’t work: they all give the same 403 message.
- Installing a newer git version (I tried
git version 2.13.3.windows.1) - have the plain URL:
- put just the username or e-mail address in the URL
- put just the username or e-mail address in the URL with a blank password
- for the four above, add the caching credential helper then add a credential:
git config --local credential.helper cachegit config --local credential.https://gitlab.com.username wiert
You get this log:
Pushing to https://gitlab.com/wiert.me/examples/sql-examples.git
git: 'credential-cache' is not a git command. See 'git --help'.
remote: HTTP Basic: Access denied
fatal: Authentication failed for 'https://gitlab.com/wiert.me/examples/sql-examples.git/'
What could work
The first thing that works is to include the actual password in the repository URL like this:
- https://wiert:password@gitlab.com/wiert.me/examples/sql-examples.git
- https://jeroen.gitlab.com%40pluimers.com:password@gitlab.com/wiert.me/examples/sql-examples.git
When you enter the correct password, everything is fine. Except that the password is stored as plain text on disk.
What works
The real solution on Windows is to use the Windows Credential Manager. I found this because of the 5th failure above.
To see which username/password combinations have been stored or add your own, you can start the Credential Manager on the command-line like this (each Windows version seems to have a different path to the UI from the control panel; the console trick just works on all Windows versions I tested):
%windir%\explorer.exe shell:::{1206F5F1-0569-412C-8FEC-3204630DFB70}Note the above was the reason for writing List of Shell GUIDs for various Windows versions for use in shortcuts and batch files.
What might work on non-Windows systems
I have the impression that the “cached” credential manager will work on non-Windows systems, but need to find some time testing that on multiple platforms. Stay tuned (:
For that I need to look into at least these:
- [WayBack] msysgit – git: ‘credential-cache’ is not a git command – Stack Overflow
- [WayBack] windows – Remove credentials from Git – Stack Overflow
- [WayBack] git – Is there a way to skip password typing when using https:// on GitHub? – Stack Overflow
- [WayBack] Git – gitcredentials Documentation
–jeroen
Share this:
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitHub, GitLab, Source Code Management | Leave a Comment »
Reminder to self: make a list of URL suffixes to show branch diagrams of repositories
Posted by jpluimers on 2018/12/18
One of the BitBucket features I like a lot is that in the commit history, you see the branches involved in a nice diagram on the left side of the commits: https://bitbucket.org/pypy/pypy/commits
BitBucket used to be popular to host public repositories, but from a public perspective, they are on the decline for that (they even removed the [once popular] bitbucket.org/explore page and [WayBack] will not re-introduce it).
Right now, only major git based hosters still have explore pages:
- https://gitlab.com/explore
- https://github.com/explore and https://github.com/trending (it [used to be called] https://github.com/repositories)
So it makes sense to see where they provide diagrams of branches, so here are some examples to go from a project to the graph:
- https://bitbucket.org/pypy/pypy
- https://gitlab.com/gitlab-org/gitlab-ce
- https://gitlab.com/gitlab-org/gitlab-ce/network/master (in the Web UI you click on Repository, then on Graph)
- https://github.com/gitlabhq/gitlabhq
- https://github.com/gitlabhq/gitlabhq/network (in the Web UI, click on Insights->Graphs, then wait and click on Network; if there are many branches, this page will not load)
- https://github.com/python/cpython
–jeroen
Share this:
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitHub, GitLab, Mercurial/Hg, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 