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

Renaming the Extension name, Github Repo and files #330

Closed
a-bentofreire opened this issue Sep 7, 2024 · 10 comments
Closed

Renaming the Extension name, Github Repo and files #330

a-bentofreire opened this issue Sep 7, 2024 · 10 comments

Comments

@a-bentofreire
Copy link

Hi,
I'm the owner of the extension BracketsToIX which is on the repo: https://github.com/a-bentofreire/bracketstoix

I would like to:

  1. change my repo name to: editortoix
  2. move all the files and folders to a subfolder called phoenix
  3. have the name visible to the user as EditorToIX instead of BracketsToIX, the internal ids can be the same as long as to the user is called EditorToIX

Is there a problem with these changes regarding the .github/workflows ?

@abose
Copy link
Member

abose commented Sep 7, 2024

@a-bentofreire do you have to do this in brackets or Phoenix code?

@a-bentofreire
Copy link
Author

a-bentofreire commented Sep 7, 2024

I'm sorry, but your question isn't clear.
I'm talking about renaming my repo name, files and folders on my github repo, including the display name but keeping the name on the package.json, but it must work with Phoenix code workflows in order for the user on Phoenix code see the same extension but with a different display name.

the github repo is https://github.com/a-bentofreire/bracketstoix will be change to https://github.com/a-bentofreire/editortoix.
According to https://github.com/phcode-dev/phoenix/wiki/How-To-Write-Extensions-And-Themes , as long as I create a zip it should be ok.
the package name will continue to be: github-a-bentofreire-bracketstoix but the repo name will be editortoix, and the zip file will be extension.zip. Is this correct?

@a-bentofreire
Copy link
Author

I found the solution.

@abose
Copy link
Member

abose commented Sep 7, 2024

@a-bentofreire The only thing to note is that the extension id is tied to the github user:repo handle. Everything else can be changed by just updating the fields in package.json . did it work as expected?

@a-bentofreire a-bentofreire reopened this Sep 7, 2024
@a-bentofreire
Copy link
Author

Hi.
Yes, it worked. It didn't in the first time because I dragged the file to the description, not to the attached files.
So, it looks like it will update, it's still not available with the new name on extensions manager, but I just did it a few minutes ago
I remember, you mention that you remove the duplicate. That is important, since I see there is already 93 downloads of the duplicate extension, that is the old BracketsToIX but none of the new version.

@a-bentofreire
Copy link
Author

It did publish correctly after all the changes that I did.
Internal the id it's the same : "github-a-bentofreire-bracketstoix" but visually it's EditorToIX.
The other one called BracketsToIX should be deleted, someone fork it.
EditorToIX

@abose
Copy link
Member

abose commented Sep 7, 2024

@a-bentofreire so the pending thing is to delete brackets to ix from our end right?

@a-bentofreire
Copy link
Author

a-bentofreire commented Sep 8, 2024

Correct, delete the bracketstoix on your end, which was a fork done by someone else,
please, just bear in mind that EditorToIX internal name is github-a-bentofreire-bracketstoix and this shoudn't be deleted

@abose
Copy link
Member

abose commented Sep 14, 2024

@a-bentofreire Extension with id bracketstoix removed. Got busy last week with the new release, sorry for the delay.

@a-bentofreire
Copy link
Author

@abose Thank you so much. I tried to open a phcode on a private window, and search for toix, and now it only shows my extension. This issue is solved.

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

No branches or pull requests

2 participants