From 2a271852894b44f0b2f32f4d941fa2e4caaa5e5f Mon Sep 17 00:00:00 2001 From: "huang.zhiping" Date: Sat, 28 Apr 2018 18:44:27 +0800 Subject: [PATCH] fix error url Change-Id: Ia6fa4a41ff41d553ea65a3a876e5cdc5cca8f814 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 899fb95..41e9e28 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ There are two ways to create the boilerplate for the puppet module. ### Locally - 1. Clone locally the [puppet-openstack-cookiecutter](https://git.openstack.org/openstack/cgit/puppet-openstack-cookiecutter) repository. + 1. Clone locally the [puppet-openstack-cookiecutter](https://git.openstack.org/cgit/openstack/puppet-openstack-cookiecutter/) repository. 2. Run `cookiecutter /path/to/cloned/repo` ### Remotely (ie. using a git repo) @@ -28,4 +28,4 @@ There are two ways to create the boilerplate for the puppet module. ## What's next -Once the boilerplate created, in order to be compliant with the other modules, the files managed by [msync](https://github.com/puppet-community/modulesync), (or [configs](https://git.openstack.org/openstack/cgit/puppet-modulesync-configs)) needs to be in the project folder. Once synced module is ready, announce its existence to the ML, make the proper patch to openstack-infra and finally wait for the reviews to do the rest. +Once the boilerplate created, in order to be compliant with the other modules, the files managed by [msync](https://github.com/puppet-community/modulesync), (or [configs](https://git.openstack.org/cgit/openstack/puppet-modulesync-configs/)) needs to be in the project folder. Once synced module is ready, announce its existence to the ML, make the proper patch to openstack-infra and finally wait for the reviews to do the rest.