Re: [Scons-dev] Migrating issues from Tigris to GitHub

Is there any way to enumerate all the existing PR/Issues and overwrite only the issues? (and/or items without corresponding changelists)? That'd allow us to re-use the existing 3k or so aborted migrated issues. -Bill On Fri, Jan 26, 2018 at 1:34 PM, Andrew Featherstone <

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Hi All, I've addressed all the issues that I'm aware of with the importing of issues into GitHub. I don't kniow if there's anything we can do to fix the existing changes to the merge requests, but AFAICT we're ready to give this another go. Regards, Andrew On 3 January 2018 at 18:37, Bill

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Crap. It looks like the migration script overwrote existing pull requests. They are all gone and replaced with migrated bugs. Let me see if I can get ahold of github and get them restored.. -Bill On Tue, Jan 2, 2018 at 1:39 PM, Bill Deegan wrote: > o.k. I'm going to

Re: [Scons-dev] Migrating issues from Tigris to GitHub

o.k. I'm going to disable the issues and remove the lock on the scons/scons repo for now. I'll fork out another for use trying out any fixes before rolling out to the main repo. -Bill On Tue, Jan 2, 2018 at 12:57 PM, Andrew Featherstone < andrew.featherst...@cantab.net> wrote: > Hi All, > > Yes

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Hi All, Yes you're right, it seems that "every pull request is an issue, but not every issue is a pull request." as noted at https://developer.github.com/ v3/issues/#list-issues. I've raised a couple of issues at https://github.com/SCons/tigris-to-github/issues to submit my fixes against. I'm not

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Yes the 36 Pull Request we had got overwritten with the bug information for 1-36. If possible i think it would be best to move the pull request to the newest numbers so all the cross references to issue numbers can stay the same. Also another issue I saw was that # sign will link to other

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Hi Bill, I'm glad you persevered. No I've not put any effort into making this work with Python 2. There's some crude retry mechanisms in the implementation. By the look of https://github.com/scons/scons/issues this is still trundling on, as the issue count keeps going up when I refresh the

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Got past that. Requires python 3 and a few modules. Running now but just got the folllowing: GitHub repository for issues: scons/scons GitHub repository for attachments: scons/tigris-issue-attachments 1 2 3 4 5 6 7 8 422 {'message': 'Validation Failed', 'errors': [], 'documentation_url': '

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Andrew, Great! I'll see if I can kick off the migration today and start 2018 on a high note! Thanks for all the hard work! -Bill On Mon, Jan 1, 2018 at 6:23 AM, Andrew Featherstone < andrew.featherst...@cantab.net> wrote: > Done. > > On 29 December 2017 at 17:28, Bill Deegan

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Done. On 29 December 2017 at 17:28, Bill Deegan wrote: > Can you send a pull request to scons/tigris-to-github ? > > On Fri, Dec 29, 2017 at 3:37 AM, Andrew Featherstone < > andrew.featherst...@cantab.net> wrote: > >> I've just check this morning that it's able to

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Can you send a pull request to scons/tigris-to-github ? On Fri, Dec 29, 2017 at 3:37 AM, Andrew Featherstone < andrew.featherst...@cantab.net> wrote: > I've just check this morning that it's able to work with an organization's > repos and not just an individual's. If you don't want to solicit

Re: [Scons-dev] Migrating issues from Tigris to GitHub

I've just check this morning that it's able to work with an organization's repos and not just an individual's. If you don't want to solicit feedback on the users' mailing list, then the next step is to perform the migration. So, to move things forward: 1. Clone my repo. 2. Call python

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Yes. Sorry I didn't see the link in the existing markup. That looks good to me. So to move forward (migrate bugs to scons/scons and attachments to scons/tigris-issue-attachements/ ) what do I need to do? Thanks, Bill On Thu, Dec 28, 2017 at 12:56 PM, Andrew Featherstone <

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Hi Bill, I'm not sure I follow you. The issue numbers and the Tigris 'attachment IDs' (used as the folder names) aren't the same value. Where issues have attachments they are reffered to in the issue by name, and the URL is included in the Markdown. As an example, see

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Can you add to the github bug a link to the github attachment repo where appropriate? (so you don't have to go look for the repo and then the issue number folder.) On Thu, Dec 28, 2017 at 11:51 AM, Daniel Moody wrote: > I think it's awesome, looks great fully support moving

Re: [Scons-dev] Migrating issues from Tigris to GitHub

I think it's awesome, looks great fully support moving forward with this! Good work! On Dec 28, 2017 2:36 PM, "Andrew Featherstone" < andrew.featherst...@cantab.net> wrote: > Hi All, > > Any comments or feedback on this? > > Regards, > Andrew > > > On 17 December 2017 at 18:58, Bill Deegan

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Hi All, Any comments or feedback on this? Regards, Andrew On 17 December 2017 at 18:58, Bill Deegan wrote: > Great work! > I'll try and set aside some time to review it this week. > > -Bill > > On Sat, Dec 16, 2017 at 6:44 PM, Andrew Featherstone < >