Figure out the strategy for this repo vs the existing repo.
We can either try to merge (ideally with history) -- but then figure out what to do with existing issues, etc. -- or we can just make this repo be the drop-in replacement for the previous one.
If decide to do a drop-in replacement
Rename existing Script Lab repo to "script-lab-older"
Rename this one to "script-lab" and make it public
Change script-lab-older readme to explain this.
Before we do it with the real repo, we should try it with a fake one to see how redirects & etc work (namely, because we will name the new repo same as old, redirects should break, which is OK -- but just make sure that everything else works as expected)
Zlatkovsky
commented
5 years ago
Figure out the strategy for this repo vs the existing repo.
We can either try to merge (ideally with history) -- but then figure out what to do with existing issues, etc. -- or we can just make this repo be the drop-in replacement for the previous one.
If decide to do a drop-in replacement
Before we do it with the real repo, we should try it with a fake one to see how redirects & etc work (namely, because we will name the new repo same as old, redirects should break, which is OK -- but just make sure that everything else works as expected)