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

change repo name #1

Open
MattDMo opened this issue Nov 5, 2015 · 1 comment
Open

change repo name #1

MattDMo opened this issue Nov 5, 2015 · 1 comment

Comments

@MattDMo
Copy link

MattDMo commented Nov 5, 2015

Based on previous experience, I would strongly suggest changing your repo's name to something like logcat-sublime. The problem with naming it with an extension that's used by Sublime (.tmLanguage, .tmTheme, etc.) is that some versions of Sublime may process the directory name, thinking it's a file name, and mess things up internally.

When I first started work on Neon, I named the repo Neon.tmTheme, and only later learned about the issues some users were having, so I changed the name to Neon-color-scheme (Github will still follow links to the old repo name, no problem), and in Package Control changed the name of the package (and hence the directory it's installed in) to Neon Color Scheme, which it's been ever since. If/when you ever submit this to Package Control (it's actually a very easy process, only taking a couple of days, max), you can name the package simply Logcat if you wish.

@leesei
Copy link
Collaborator

leesei commented Nov 10, 2015

Thanks for the suggestion.
I intended to start a new repo for uploading to Package Control as I wanted to keep the log and screenshot away from it (possibly by putting them in gh-pages branch).
I'll keep this in mind when I start the work.

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