search

chakra-core / org

Various organizational content (meetings, previews, etc)
4 stars 5 forks source link

Transition #1

Open ppenzin opened 4 years ago

ppenzin commented 4 years ago

@chakra-core/core I've fiddled with forking ChakraCore, but that ended up having some limitations. I deleted the fork, sorry if that caused trouble. Creating this issue as we don't have everybody on discord.

Mainly, I can't seem to transfer issues from Microsft/ChakraCore. Does anybody know how to transfer to the fork? Would creating "new" repo with the same history solve that?

"Repo transfer" would solve this, but it requires admin access on Microsoft side and would abruptly break CI there.

Any ideas welcome.

chicoxyzzy commented 4 years ago

As fat as I know, repo transfer is the only way to move issues. We also can try to ask help from GitHub staff.

ppenzin commented 4 years ago

Bummer. I was hoping "Transfer issue" would be of any help, but apparently that only works within the same org or account.

There is of course the tried and tested method of opening issues in the new place referencing issues in the old place, though it is a bit of work.

rhuanjl commented 4 years ago

As a worst case scenario if we go a month without a clear plan for how/when we can transition the repo I guess I could spend a day writing a node script to use puppetteer to move the issues over that would be "fun" :p.

ppenzin commented 4 years ago

Yeah, I am not sure if we are allowed to have that much fun :)

Can we create a landing issue in this repo which would point out that transition has started and merge a pointer to it into readme at the main repo (and also probably add a 'pinned' issue there).

I'd like to point people to the place where work is getting done and if we have enough interest we can start setting source area for landing fixes.