openstack
/
openstack-chef-specs
Code Issues Proposed changes

Replacing the HTTP protocal with HTTPS 

Change-Id: Ie5968f037656d1a64723a925f07d5ed12b25ff7a
This commit is contained in:
zhangshj 2019-01-13 14:49:25 +08:00 committed by Jens Harbott (frickler)
parent a57a5f190b
commit ae1d6a4aef
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@ -2,8 +2,8 @@
Team and repository tags Team and repository tags
======================== ========================
.. image:: http://governance.openstack.org/badges/openstack-chef-specs.svg .. image:: https://governance.openstack.org/badges/openstack-chef-specs.svg
:target: http://governance.openstack.org/reference/tags/index.html :target: https://governance.openstack.org/reference/tags/index.html
.. Change things from this point on .. Change things from this point on
@ -37,7 +37,7 @@ Prior to the Juno development cycle, this repository was not used for spec
reviews. Reviews prior to Juno were completed entirely through Launchpad reviews. Reviews prior to Juno were completed entirely through Launchpad
blueprints:: blueprints::
http://blueprints.launchpad.net/openstack-chef https://blueprints.launchpad.net/openstack-chef
Please note, Launchpad blueprints are still used for tracking the Please note, Launchpad blueprints are still used for tracking the
current status of blueprints. For more information, see:: current status of blueprints. For more information, see::
@ -46,7 +46,7 @@ current status of blueprints. For more information, see::
For more information about working with gerrit, see:: For more information about working with gerrit, see::
http://docs.openstack.org/infra/manual/developers.html#development-workflow https://docs.openstack.org/infra/manual/developers.html#development-workflow
To validate that the specification is syntactically correct (i.e. get more To validate that the specification is syntactically correct (i.e. get more
confidence in the Jenkins result), please execute the following command:: confidence in the Jenkins result), please execute the following command::