You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This pull request adds the following:
Script Bootstrap
----------------
`script/bootstrap`, conventionally used to get new clones up and running
in a single command. This one checks for Ruby and Mongo and then,
assuming both are present, installs (if necessary) and runs bundler. The
idea is that there are only two things new contributors ever need to do.
1. git clone
2. script/bootstrap
If we really like it, we can make it smart enough to recommend ways to
*get* MongoDB and Ruby based on the OS, but I feel like that's a bit
overkill for a v1. The idea is that contribution should be as smooth as
possible so would-be helpers can start helping immediately. The script
should remain idempotent so if changes are made to the application,
existing contributors can pull, run script/bootstrap, and be ready to go
without borking their existing dev instance.
One thing this does as a side effect is specify a path for vendored gems
and binstubs, this is why the .gitignore changes were made.
.ruby-version
-------------
Specify a Ruby version using the ruby manager agnostic version of an
rvmrc.
CONTRIBUTING.md
---------------
When you create a new Pull Request or Issue, GitHub will highlight a
block above the new issue/PR title calling attention to the repository's
CONTRIBUTING.md file, should one exist. This is an expanded version of
the Helping Out section from the README.
If you're asking a question about Hackety Hack itself, check out the [Hackety
6
+
Hack repository][hh].
7
+
Otherwise, go ahead and open an [issue][issues] and let us know!
8
+
9
+
## Bugs ##
10
+
11
+
If you notice a bug in Hackety-Hack.com, this is the place to let us know.
12
+
Please tell us:
13
+
14
+
- Which url the bug occurred at
15
+
- What steps we can take to reproduce this bug
16
+
- If the bug is visual, including a screenshot is really helpful.
17
+
18
+
## Pull Requests ##
19
+
20
+
We :heart: pull requests; We :heart::blue_heart::green_heart: Pull Requests with tests. In fact, we don't want to accept pull requests without relevant tests. If you're not sure if the feature you want is welcome and you want to check with us, feel free to create [an issue][issues] or if you're just totally driven to make it happen, spike it out and open a pull request, but we'll ask you to add tests before it's merged.
Copy file name to clipboardExpand all lines: README.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,24 @@ If you have any experience writing Rails apps, feel free to help out, we're open
11
11
+**Test your code**, we really can't stress this enough, ideally you should be practicing [TDD][tdd] and writing tests before you even write your code. If you don't test your code, we have no way of knowing if it works properly so please do test.
12
12
+**If it's a major feature, file an issue**, if you file an issue we can discuss certain aspects of the new feature with you and ensure it's a good fit for hackety-hack.com.
13
13
14
-
Additionally, if you're _not_ a developer and you have a feature you'd really like to see on the site, file an issue and we'll be sure to look into it on your behalf.
14
+
## Getting Started ##
15
+
16
+
Once you've cloned this repository, running `script/bootstrap` should tell you everything you need to know.
17
+
18
+
Dependencies for the curious:
19
+
20
+
- Ruby: 1.9.3 is preferred.
21
+
- MongoDB: 2.2.x or 2.4.x
22
+
23
+
As long as you have those things, the script will handle the rest as best it can, including installing the gem dependencies with Bundler.
24
+
25
+
If the tests aren't passing when you clone, open [an issue][issues] or drop into
26
+
[#hacketyhack on freenode][irc].
27
+
28
+
Additionally, if you're _not_ a developer and you have a feature you'd really like to see on the site, file [an issue][issues] and we'll be sure to look into it on your behalf.
0 commit comments