Repository navigation
Use name "SafeEyes" or "Safe Eyes" consistently? #820
Description
Hi!
I noticed that sometimes it's "Safe Eyes" with a space and sometimes "SafeEyes" without, both in here and on https://slgobinath.github.io/SafeEyes/ . Would you welcome pull requests making it consistent one way or another? If yes, which of the two is your preference?
Best, Sebastian
Reacted by Gobinath and deltragon
Activity
slgobinath commentedon Dec 25, 2025
Hi,
I named it Safe Eyes with space but wasn't too conscious about the space or any other conventions.
I was learning a lot part of the project. For example later I regret naming the repository using title case not
safeeyes.If we pick between two I vote for
Safe Eyes.archisman-panigrahi commentedon Dec 25, 2025
@slgobinath You can still rename the repository to
safeeyes. The old link will automatically redirect to the new link. I have done that with many of my projectshartwork commentedon Dec 25, 2025
Thanks for your quick replies! I'll see about a pull request now…
slgobinath commentedon Dec 25, 2025
@archisman-panigrahi I am all in to rename the repository if there's no consequences but I will leave it to your decision.
slgobinath commentedon Dec 25, 2025
Happy Holidays to both of you!!!
archisman-panigrahi commentedon Dec 25, 2025
There should not be any major consequences in renaming from my experience. The github website and links will be forwarded to the new ones. Images on readme and screenshots may get broken but we can easily fix it.
And on the website hearder, let's rename "SafeEyes" to "Safe Eyes"
archisman-panigrahi commentedon Dec 25, 2025
Happy holidays!
hartwork commentedon Dec 25, 2025
Happy holidays to you two also! 🙏 🎄
hartwork commentedon Dec 25, 2025
@slgobinath is the website in https://github.com/slgobinath/slgobinath.github.io and it's non-public? Am I looking in the wrong place?
hartwork commentedon Dec 25, 2025
I made #821 for non-translation strings. Translation strings are a bit more tricky, I will give that a shot also. Upcoming…
archisman-panigrahi commentedon Dec 25, 2025
Here is the webpage code https://github.com/slgobinath/SafeEyes/tree/gh-pages
slgobinath commentedon Dec 25, 2025
@archisman-panigrahi do you have permission to rename the repository?
archisman-panigrahi commentedon Dec 25, 2025
No, I can't access settings. Can you rename it please?
hartwork commentedon Dec 25, 2025
I'll prepare the in-code URL rename PR…
slgobinath commentedon Dec 25, 2025
Renamed the repo. Yew website code is in gh-pages
hartwork commentedon Dec 25, 2025
I think the rename broken existing links to https://slgobinath.github.io/SafeEyes/ 🤔 (proof)
hartwork commentedon Dec 25, 2025
I have related commit d623c6c now in PR #823 if you want to go forward with the new name.
hartwork commentedon Dec 25, 2025
Different branch — I see! 👍
archisman-panigrahi commentedon Dec 25, 2025
Old links are not broken. For example, see https://github.com/slgobinath/SafeEyes/blob/master/safeeyes/platform/io.github.slgobinath.SafeEyes.metainfo.xml#L56
Merge pull request #823 from hartwork/sync-repository-references-afte…
Merge pull request #822 from hartwork/issue-820-use-name-safe-eyes-in…
archisman-panigrahi commentedon Dec 25, 2025
I updated weblate with the upstream changes and also updated the website there
hartwork commentedon Dec 26, 2025
@archisman-panigrahi yes but https://slgobinath.github.io/SafeEyes/ is different and did break through the rename because it's https://slgobinath.github.io/safeeyes/ now.
Merge pull request #824 from hartwork/gh-pages-issue-820
Merge pull request #821 from hartwork/issue-820-use-name-safe-eyes-mo…
archisman-panigrahi commentedon Dec 27, 2025
For the renamed website, I have updated the AUR package. I'll contact other distro package maintainers to update it