Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First step: move all known issues for the existing TextMate grammar to this repo #1

Closed
daviwil opened this issue May 24, 2016 · 7 comments

Comments

@daviwil
Copy link
Contributor

daviwil commented May 24, 2016

Since we're now centralizing development of the TextMate definition for PowerShell in this repo, it'd be good to find all known issues with the current state of the syntax definition and move them to this repo. It'd be great to have some help doing this (especially if someone can find a way to automate it 😉)

Here are some starting points:

Visual Studio Code

Sublime Text

Atom

@guillermooo @jugglingnutcase @vors @Jaykul @gravejester

@hashhar
Copy link

hashhar commented Aug 31, 2016

I can try writing a script to import the issues. I will let you know within the week.

@jrsconfitto
Copy link

jrsconfitto commented Aug 31, 2016

I just used this application to do it: https://github-issue-mover.appspot.com/

Looks like it's run by @google: see the code in their org: https://github.com/google/github-issue-mover

It was pretty easy to migrate the issues with: someone with access to the original repo with issues need to auth the app and then paste a couple links with the old issue and this repository.

Edit: it doesn't move a ton of issues easily that I can see, though. Maybe a script would work better for the SublimeText owners.

@hashhar
Copy link

hashhar commented Aug 31, 2016

@jugglingnutcase I think this will serve well for repos hosted on GitHub. And it seems like quite a lot of people use it. The only problem is that it closes the original issues. We can maybe fork it to fix that.

@jrsconfitto
Copy link

I'm fine with it closing the original issue on my repo, I guess other people may want a different behavior, though.

@hashhar
Copy link

hashhar commented Aug 31, 2016

@jugglingnutcase I'll try and see if I can manage to fork the repo to behave that way.

@hashhar
Copy link

hashhar commented Sep 16, 2016

I'm sorry but I couldn't get the tool to work that way. I'll have to write a script. Sorry for the delay.

@omniomi
Copy link
Contributor

omniomi commented May 21, 2018

Closing as the vast majority of issues were indeed moved or resubmitted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants