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
Development.md
: How to Develop Meteor Itself
#8267
Commits on Feb 17, 2017
Commits on Feb 20, 2017
-
-
Add section on commit messages.
While the title is obvious, I guess I should add a commit description here for the sake of fully explaining the importance of a good commit message! This commit, along with the ones before it should help make it very clear how to contribute to Meteor!
-
In addition to adding myself, this adds Hugh Willson (@hwillson) and removes past contributors not currently active.
-
-
-
Commits on Feb 28, 2017
Commits on Mar 1, 2017
-
Suggest the use an alias for frequent contribution.
Per PR suggestions, add a suggestion to make an alias for more frequent use. Also, due to difficulty of formatting aforementioned change, move unrelated Note (which didn't belong there) to a more prominent section called "Notes when running from a checkout"
Commits on Mar 2, 2017
-
Add information about the "Dev Bundle".
This moves the dev bundle step out of the "Running from checkout", simplifying those steps, but breaks things down much more in its own, new, section.
-
Thanks to @klaussner and @hwillson for these suggestions! I also changed some other trademark-y things. 😉
Commits on Mar 9, 2017
-
Add a header to
Development.md
explaining its purpose.Great suggestion, @benjamn. Thanks.
-
Fix header type of "Notes when running from a checkout".
This was inadvertently set as a "H1" (`#`) but should have been nested within the "Running from a Git checkout" section as an "H2" (`##`).