Change URLs to point to Github

[ged]

Since Bitbucket is shutting down support for Mercurial, and most of the work is done via git nowadays, there’s no reason to keep ruby-pg there any longer.

[larskanis]

LGTM

[cbandy]

iiuc, these should be curly then square brackets, e.g. {text}[url]

[cbandy]

It might be possible to use a relative link here, [certs] or [certs/].

[ged]

Relative links would only work when rendered on Github, right?

[cbandy]

Yes, true. The word "directory" made me think of a local checkout.

Since this is about installation, an absolute URL makes sense.

[larskanis]

@ged I just got a notification from the mail system that my mail to ged at faeriemud dot org couldn't be delivered. So here is it again:

Hi Michael,

I fully agree with you regarding to moving to Github. I could also live
with Gitlab or Bitbucket, but I never really know what I'm doing when
using Mercurial ;-). Since we already have this mirror on Github, it's
best to just label it the canonical repository now.

Regarding issues migration I did a quick attempt with the following
result: https://github.com/larskanis/importtest/issues
I used this tool with some minor changes:
https://github.com/jeffwidman/bitbucket-issue-migration
All issues have the same number on github, so that references still fit.
If it's OK, I can repeat the import to https://github.com/ged/ruby-pg

--
Regards,
Lars

[ged]

Sorry about the email bounce. We've been having mysterious hardware issues on our mailserver.

And yeah, please do import the issues, @larskanis . That looks great!

I'll fix the issues from your review when I get home tonight @cbandy. Thanks for the review.

[larskanis]

@ged Issue migration to GitHub ged/ruby-pg failes probably due to permissions with 404 like here: jeffwidman/bitbucket-issue-migration#88
Could you please set temporary admin permission for me? Alternatively I can send you the patch and commands for doing the migration on your own.

[ged]

You apparently can't grant admin permissions on personal accounts, but I'm happy to run the script myself.

[larskanis]

@ged Issue migration should work like so:

$ git clone https://github.com/larskanis/bitbucket-issue-migration --branch nickname
$ cd bitbucket-issue-migration
$ python3 -m venv ./py3   # As described in the README
$ source ./py3/bin/activate
$ pip3 install -r requirements.pip

Now run the first batch of issues:

python3 migrate.py ged/ruby-pg ged/ruby-pg ged

This however stopped for me at issue 34 complaining about the missing tag "Documentation". So I renamed "documentation" to "Documentation" on the github page and restarted with:

python3 migrate.py ged/ruby-pg ged/ruby-pg ged -f 34

Then it did run through all remaining 265 issues.

[larskanis]

I just noticed, that we already are at #43 due to the pull requests, that are already on this repository and due to the fact that github uses a common counter for issues and pull requests. So we probably either can't migrate issues 1 to 43 from bitbucket or have to add an offset of 43 to all the issues.

[ged]

Ah, right okay. I think that since #43 is 8 years old at this point just omitting them should be fine. It might lead to weirdness with old links, but that's probably inevitable anyway.

[ged]

Okay, most of the issues are pulled over. I had a few false starts, so the earliest tickets have mismatched numbers, but everything after #47 or so should be correct.

I'll shut down the Bitbucket project later tonight, then maybe push a release when you merge in the record encoder stuff?

[larskanis]

@ged imported issues look good - thanks Michael! So I think the bitbucket project can be shut down.

One remaining issue is that the Appveyor project is still linked to bitbucket instead of GitHub. Can you please fix it and possibly update the badge link in the Readme?