-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Rename this repository to "opensourcedesign.net" #172
Comments
I thought it was a github thing? |
You can see all the places it's referenced here: |
I can do a PR replacing all those with opensourcedesign.net if you like |
Glancing at them I don't think changing any of those (though they should be changed) will affect the deployment process. They all look like they're part of documentation? |
I changed it to opensourcedesign.net again so we finally do it and fix stuff going forward. ;) The newsfeed was fixed by changing the places where it was still "opensourcedesign.github.io" as @elioqoshi mentioned. However, Jobs and Events are still broken, seemingly cause there’s a 404 on: Any idea @simonv3 @elioqoshi @evalica? Maybe this is also a good time to move the events and jobs repos into the website repo to remove possible sources of error? |
Moving the events and jobs folder out into the root, with or without "_" makes it work strangely, but then other stuff is broken so not sure if this is a good way. If it’s not fixable with something obvious, we can also simply roll it back by renaming the repo back to "opensourcedesign.github.io" and reverting 87e1185 |
@jancborchardt should we consider renaming the repo back and reverting that patch? I would offer to help, but I'd probably just make a mess of it :( |
@belenbarrospena yeah, renamed it back shortly after. Will look into combining the repos, but only in a pull request. :) |
We should rename this repository to properly reflect the website name and make it more obvious for people where to contribute.
The problem we had was that when @simonv3 or I did that, the jobs and events weren't loading at all anymore on the main page. So probably it's referenced in some script or in the events/jobs repo.
The text was updated successfully, but these errors were encountered: