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

Better process to update https://cristibalan.github.io/braid #67

Open
mattmccutchen opened this issue Jun 8, 2017 · 2 comments
Open

Comments

@mattmccutchen
Copy link
Collaborator

Should we be remembering to update http://cristibalan.github.io/braid every time we update the readme, or shall we just redirect it to the repository so people can see the readme (and add any desired download links there)?

@realityforge
Copy link
Collaborator

I have thought about moving it from a separate branch into a subdirectory docs in the master branch and just have the README.md in base directory redirect to docs/README.md but never got around to doing it. We would also need to ask the owner of the repository to update the projects configuration to enable but that should not be an issue.

@mattmccutchen mattmccutchen changed the title http://cristibalan.github.io/braid is out of date Better process to update https://cristibalan.github.io/braid Jan 24, 2022
@mattmccutchen
Copy link
Collaborator Author

For the record: Our current process is to manually copy the master branch to the gh-pages branch every time we make a change that affects the web site. We may have various other options, but any of them will require cristibalan to change the repository settings, and the last time I asked about that, I got no response.

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