* Bruno Oliveira <nicodde...@gmail.com> [2015-06-05 03:06:35 +0000]:
> After a few changes to the script, I have migrated all issues to a
> temporary repository at:
> https://github.com/nicoddemus/pytest-issues-migration.
> 
> Moved issues retain:
> - body
> - creation date
> - comments
> - kind and component (added as labels)

Awesome, thanks for the great work!

> Issue and comment authors are added to each issue or comment as a note in
> the body, but the issue author will always be the person that ran the
> script (this is a limitation of the GitHub import API). Is this a problem?
> When doing the final migration, which user should we use?

I suggest creating a new user for the migration so it's immediately
apparent that's not the real issue author.

For example, a pytest-dev/pytest-bot/pytest-issue-migration/... user
with the pytest logo as avatar.

> Any feedback on how we can improve the import process?

I think the "Bitbucket / originally reported by" footer should be at
the top (before the issue text) instead - again so it's immediately
apparent what's going on.

Also, stuff inside <> seems to be removed?
See 
https://github.com/nicoddemus/pytest-issues-migration/issues/6#issuecomment-109143858
for example.

Some other ideas which might or might not be worth the effort:

- Rewrite full links to an issue (as opposed to #nnn identifiers) to
  point to the correct/new location (or to use #nnn instead)

- Rewrite links to PRs, if PRs will be migrated

- Rewrite those "-> <<cset ...>>" comments to point at git commits
  (when the repo is migrated) instead of hg changesets).
  (See link above for a [broken] example)

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/

Attachment: pgpCivyz0PfCm.pgp
Description: PGP signature

_______________________________________________
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Reply via email to