From c40c6a1af5ee8bc83f9ea9b4c99dcf2cfbf4b66a Mon Sep 17 00:00:00 2001 From: Sam Gleske <sag47@drexel.edu> Date: Tue, 12 Nov 2013 10:55:09 -0500 Subject: [PATCH] Update contribution encouragement in README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 77314c0..474a056 100644 --- a/README.md +++ b/README.md @@ -38,9 +38,9 @@ There are a couple ways you can try to get help. You can [file an issue](https: --- # Contributing -I enjoy contributions and encourage them! You should add your code to my project and make your mark. I only make a few simple requests in order to contribute. +I enjoy contributions and encourage them! You should add your code to my project and make your mark. [Pick off an issue](https://github.com/sag47/gitlab-mirrors/issues) or implement a feature filling your need. I only make a few simple requests in order to contribute. -* Test your own work before submitting a pull request. Most of this project is bash code so we do not have the luxury of a test driven frame work to assist our development. Needless to say I will be sure to test it myself before it ever makes it into a production release. +* Test your own work before submitting a pull request. Most of this project is bash code so we do not have the luxury of a test driven framework to assist our development. Needless to say I will be sure to test it myself before it ever makes it into a production release. * Create a feature branch with a name that does not exist in any of my branches (e.g. `feature/myfeature` or `feature-cool_feature`). This is where you should do your development. This will allow you to integrate my development with your own and ease integrating updated code if we're both concurrently developing. * When your feature is ready make a pull request to the *development* branch. Pull requests to the master branch will not be accepted. The master branch is intended to drive production systems and only stable production-ready commits will be made to it. -- GitLab