-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Setup github pages. #13
Conversation
| More seriously this should be something about how to help, | ||
e.g. reporting issues and *where* to report them (which repo etc) | ||
as well as advice on producing reproducable reports | ||
| If you encounter a bug in rspec itself you are encouraged to open up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "If you have an idea to improve RSpec or find a bug, you are encouraged to file a pull request or issue with the appropriate repository on Github."?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
This is the setup for Github pages with the content I added. You can view this at rspec.github.io. You'll note the 'default' branch for this repo is
source
this is becausemaster
needs to be used as the content for the site (a peculiarity of "root" pages domains).We should merge this branch and then base new PR's off
source
to add more content :)When we're happy with it we can CNAME rspec.info here :)
/cc @rspec/rspec