The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,860 other subscribers

Archive for the ‘BitBucket’ Category

Next Entries »

Research list: export issues from Bitbucket to import them later

Posted by jpluimers on 2017/05/10

This has been bugging me for a while: some Bitbucket repositories are abandoned but have a useful list of issues.

When forking them, you don’t get the issues and you cannot export them either (because the source repository is not yours).

Some links that might help me get started to solve this:

Being able to import from a non-exportable repository would allow me to keep issue # references in sync which would make it a lot easier for relating commit history with issues.

–jeroen

Posted in BitBucket, Development, Source Code Management | Leave a Comment »

raw.githack.com – like rawgit.com but supports bitbucket as well and runs on plain nginx

Posted by jpluimers on 2017/03/07

Found out recently that next to rawgit.com there is also raw.githack.com which contrary to the name also supports bitbucket files:

–jeroen

Posted in BitBucket, Development, DVCS - Distributed Version Control, git, githack.com, GitHub, Mercurial/Hg, rawgit, Source Code Management | Leave a Comment »

Linking commits to issues and issues to issues on BitBucket (via: Resolve issues automatically when users push code – Bitbucket – Atlassian Documentation)

Posted by jpluimers on 2015/08/13

Besides commit statements from hg or git like this:

hg commit -m “fixes , resolve ticket and see ticket and ticket in the tracker”

The best is to start with the command, then finish the comment (commands in the middle of a comment are far less reliable).

There is a whole bunch of commands for which BitBucket tries to understand conjugations of verbs:

Command “Verb” Conjugation(s)
resolve close close
closes
closed
closing
resolve fix
fix
fixed
fixes
fixing
resolve resolve resolve
resolves
resolved
resolving
reopen reopen reopen
reopens
reopening
hold hold hold
holds
holding
wontfix wontfix wontfix
invalid invaldate invalidate
invalidates
invalidated
invalidating

You can also use the word “issue” in the middle to just link to an issue like this syntax:

links to issue

Finally, you can refer from issues to change sets using a cset syntax: <<cset 2f2f8d4cae7da0e37a5ffbc81c527cb67cc56015>> where the hex number is from a URL in your commit list (for instance in https://bitbucket.org/jeroenp/fastmm/commits)

Note that linking from changesets to issues often automatically creates a back-link, but that doesn’t always work, and fixing it has very low priority (like many things on BitBucket): Issues getting linked to commits have the wrong link syntax, they show BB-6232 — Bitbucket.

–jeroen

via:

Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Source Code Management | Leave a Comment »

Moving my BitBucket mercurial repository to git was a lot harder than I hoped for (but moving to GitHub was easy)

Posted by jpluimers on 2015/06/10

After reading Converting Hg repositories to Git directed me into reading Bitbucket: Converting Hg repositories to Git I hoped moving my Mercurial repository on BitBucket to a Git repository would be something like following the steps.

It wasn’t.

First of all, hg-git on a Windows system requires Python or TortoiseHg. Neither of these I wanted to install for a one-off conversion.

So I took a throw-away Linux VM, and did the steps below. But let me first explain why.

Motivation

My motivation for moving away from BitBucket to GitHub, especially for projects containing markdown documentation.

When writing documentation in Markdown, being able to in-line reference pictures or have relative-references to other documents. This works perfectly in local Markdown tools (like MarkdownPad 2 or LightPaper).

Read the rest of this entry »

Posted in *nix, *nix-tools, BitBucket, Development, DVCS - Distributed Version Control, git, GitHub, Linux, Mercurial/Hg, openSuSE, Power User, Source Code Management, SuSE Linux | Leave a Comment »

How to add screenshot to markdown/READMEs in github repository ? (via: Stack Overflow)

Posted by jpluimers on 2015/05/20

Adding relative links to screenshots in markdown files (like README.md) works way better at GitHub than on BitBucket:

For GitHub, this works, has documentation and various places with tips:

In fact it is a reason for some people to move public projects from Bitbucket to GitHub.

For private repositories that is different as GitHub charges for private repositories, but BitBucket has free private repositories.

Note: if you go the npm way, then you might want to have absolute URLs: Add images to readme.md in GitHub – Stack Overflow.

–jeroen

via: git – How to add screenshot to READMEs in github repository ? – Stack Overflow.

Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitHub, MarkDown, Mercurial/Hg, Power User, Source Code Management, SourceTree | Leave a Comment »

Resolve issues automatically when users push code in Bitbucket and GitHub

Posted by jpluimers on 2015/05/14

I tend to forget some of the keywords you can put into BitBucket commit messages to relate them to certain issues/bugs/tickets

Read the rest of this entry »

Posted in BitBucket, Development, GitHub, Software Development, Source Code Management | Leave a Comment »

CodeRage 9 Q&A: Understanding Distributed Version Control (Robert Love)

Posted by jpluimers on 2014/10/30

Session:

Understanding Distributed Version Control

This session helps developers who have been working with a Centralized Version Control System such as SVN to understand and use Distributed Version Control such as GIT or Mercurial. This session focuses primarily on GIT, but applies to Mercurial. We also cover how to use GIT from the RAD Studio IDE.

Level: Beginning
Robert Love – State of Utah

Q&A:

Read the rest of this entry »

Posted in Appmethod, BitBucket, CVS, Delphi, Delphi XE6, Delphi XE7, Development, DVCS - Distributed Version Control, git, GitHub, Mercurial/Hg, Software Development, Source Code Management, SourceTree, Subversion/SVN, TFS (Team Foundation System) | 1 Comment »

Next Entries »