Import x-terminal to fix GitHub Searches into project

[the-j0k3r]

Currently if you search on this project for anything you get 0 hits, Forked projects dont get any searches, none.

If the repo is imported/ instead of forked this isnt a problem see https://github.com/the-j0k3r/x-terminal-fork-fix-gh-project-search/search?q=test&unscoped_q=test

👍 🎉

To do this goto Create a new repo and select import at the top

Nothing is lost then simply making transition from one to other should be seamless.

An alternative way is to create a new empty repo and add a remote and rebase also very doable.

[the-j0k3r]

Also I can just transfer my import of this to you, it saves you the work, just need to rename the project after you remove this one.

Edit Ive initiated this transfer to you =)

Or alternatively transfer to bus-stop org where you can admin/dev it there.

[UziTech]

I think it would be best to transfer it to bus-stop. Do you know if there is a way to change the repository but keep the package name on atom?

[UziTech]

It looks like if I just transfer the repo to bus-stop the upstream fork will remain. https://flight-manual.atom.io/behind-atom/sections/maintaining-your-packages/#transferring-ownership

I wonder if it would work to rename the repo, import it into the same name (UziTech/x-terminal), then transfer it?

[the-j0k3r]

I can export directly to bus-stop with x-terminal name, I simply rename it to x-terminal and transfer.

[UziTech]

yes but will APM allow you to publish from the new repo?

[the-j0k3r]

Yes, Termination was imported into bus-stop, besides readme links nothing else changed.

I think you can even yourself export it to bus-stop directly, its the same procedure as above, I imported into my own account not the org as I wasnt sure if thats was OK with you.

[UziTech]

But if I transfer it how it is right now the upstream fork will remain according to https://help.github.com/en/github/administering-a-repository/transferring-a-repository

[the-j0k3r]

You dont transfer it, you import it ;) Goto https://github.com/organizations/bus-stop/repositories/new and on the next page on the top

Create a new repository

A repository contains all project files, including the revision history. Already have a project repository elsewhere? Import a repository.

No upstream fork will be marked just like in my test import instance

[UziTech]

I imported it to bus-stop. https://github.com/bus-stop/x-terminal

I'll try publishing a new version with the new repo

[UziTech]

I don't think there is a way to make APM look for the package at the new repo without transferring it.

[the-j0k3r]

It worked for Termination...

[UziTech]

I renamed it imported and transfered it. hopefully that works

[the-j0k3r]

Seems like its working OK building at least.

[UziTech]

ya and now the repo link on atom.io goes to bus-stop

[the-j0k3r]

You beat me to it.

[UziTech]

looks like actions is failing to push the new tag to APM

Git tag not found

Maybe APM just needs time to update it's cache?

[the-j0k3r]

Seems fully updated, I received 8.0.2 and it points all to bus-stop, Maybe it needed time to spread.

[the-j0k3r]

Mk log for https://github.com/bus-stop/x-terminal/runs/469502934?check_suite_focus=true says

The local branch master is behind the remote one, therefore a new version won't be published

You may want to check that remote is not set to this repo or something else, since 8.0.3 is not on offer yet.

Edit: my query shows only the expected

origin  https://github.com/bus-stop/x-terminal.git (fetch)
origin  https://github.com/bus-stop/x-terminal.git (push)

I also rerun the workflows on the failed actions, all are green now.

[the-j0k3r]

Im also wondering about the semantic release bot, doesn't it have to be installed in project?

[UziTech]

it is installed as a devdependency

[the-j0k3r]

Well idk why it wont publish 8.0.3

[UziTech]

seems like it is a common issue with APM atom/apm#873

looks like we need an admin to change the repo on their server.

[the-j0k3r]

looks like we need an admin to change the repo on their server.

admin to what?

[UziTech]

admin to atom.io

[UziTech]

atom/apm#870 (comment)

[the-j0k3r]

Im perplexed. Termination was done under same circumstances, except it not running automated releases or actions. See https://github.com/bus-stop/Termination/commits/master it was as simple as that. Zero issues with this.

have you tried a manual release via apm publish? I think that may just do it. ™️ famous last words worth a shot maybe.

[UziTech]

same error when trying to publish manually

[the-j0k3r]

hummmm bum! Those failed tags are published though shouldt they be deleted?

[UziTech]

I was able to publish v8.0.4 but only after pushing tags to this repo. atom.io's system must use some sort of repo ID instead of path.

That means I could transfer this repo to bus-stop/xterminal but the upstream fork would remain. 😕

[UziTech]

looks like we just need to contact support to remove fork.

https://git.luolix.topmunity/t5/How-to-use-Git-and-GitHub/De-forking-a-Github-repo/td-p/2785

[UziTech]

I'm going to delete bus-stop/x-terminal then transfer this repo and contact support to remove the fork

[the-j0k3r]

I guess Ill stop what Im doing then

[UziTech]

boom 🎉 Actions released v8.0.5 😁👍

[the-j0k3r]

Yea it was the setup thingy

[the-j0k3r]

yep this issue is not fixed though

[UziTech]

true. I submitted a request to remove the upstream fork.

[the-j0k3r]

I would have thought fixing atom.io would have been more likely, lets see =)

[the-j0k3r]

Seems fixed... That was fast... hopefully releasing still works.