From df99fe96f6f2c100fab82a91c0d73235b9659383 Mon Sep 17 00:00:00 2001 From: Yang Luo Date: Sun, 9 Oct 2016 09:44:35 -0700 Subject: [PATCH] Fix the wrong links in opensource/code.md --- opensource/code.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/opensource/code.md b/opensource/code.md index 82ccb574f33..90b72174a61 100644 --- a/opensource/code.md +++ b/opensource/code.md @@ -28,36 +28,36 @@ If you are an experienced open source contributor you may be familiar with this workflow. If you are new or just need reminders, the steps below link to more detailed documentation in Docker's project contributors guide. -1. Get the software you need. This explains how to install a couple of tools used in our development environment. What you need (or don't need) might surprise you. -2. Configure Git and fork the repo. Your Git configuration can make it easier for you to contribute. Configuration is especially key if are new to contributing or to Docker. -3. Learn to work with the Docker development container. Docker developers run `docker` in `docker`. If you are a geek, this is a pretty cool experience. -4. Claim an issue to work on. We created a filter listing all open and unclaimed issues for Docker. 5. Work on the +href="http://docs.docker.com/opensource/workflow/work-issue/" target="_blank">Work on the issue. If you change or add code or docs to a project, you should test your changes as you work. This page explains how to + href="http://docs.docker.com/opensource/project/test-and-docs/" target="_blank">how to test in our development environment. Also, remember to always **sign your commits** as you work! To sign your @@ -68,7 +68,7 @@ issue. If you don't sign Gordon will get you! -6. Create a +6. Create a pull request. If you make a change to fix an issue, add reference to the issue in the pull @@ -81,6 +81,6 @@ pull request. needs](code.md#what-is-the-pre-pull-request-checklist). -7. Participate in the pull request review till a successful merge.