Closed mysterycommand closed 8 years ago
@Purple906, look at my commit messages. I've been trying to follow the AngularJS team's commit message guidelines … particular the sections about "type", "scope", and "subject". It'll take a little experience and some getting used to for you, but starting now will help you organize your thoughts around what's just happened (what's in this commit). Also, the other people on your team will appreciate the clarity of your commit messages.
Also, when you have a chance to look over this, could you leave a message with a 👍 in it (that's :+1:
)? It's sort of an informal way to say, "I've reviewed this and approve of merging it into master".
In future PRs, when you have questions or comments you can leave messages on the PR and once everything's resolved just drop a 👍 … and that's called code review. I think we can really learn a lot from this process. I'll leave you a thumb on your PRs when I think they're good to merge.
Make sense? Sound good?
@Purple906, this just adds a "boilerplate" or "noop (no operation)"
.travis.yml
file that tells Travis CI what to do with new pull requests (right now it won't tell it to do anything).