You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -47,7 +51,7 @@ After completing it and fixing the `TODO`s you can amend the previous commit
47
51
using `git commit --amend` or create a new commit for the changes using `git
48
52
commit`.
49
53
50
-
### Create the local development environment
54
+
####Create the local development environment
51
55
52
56
To start the development, you need to make sure your environment is correctly
53
57
setup. One way to do this is by using a virtual environment and installing all
@@ -66,7 +70,7 @@ you can open a python interpreter and import your package modules and pick up
66
70
any local changes without the need to reinstall. You can now run tools
67
71
directly, like `pytest`.
68
72
69
-
### Verify the new repository is healthy using `nox`
73
+
####Verify the new repository is healthy using `nox`
70
74
71
75
If you prefer to keep your virtual enviroment cleaner and avoid installing development dependencies, you can also use `nox` to create isolated environments for you:
72
76
@@ -89,7 +93,7 @@ which will run linters and tests.
89
93
Otherwise `nox` will create many virtual environments each time you run it,
90
94
which is **very** slow.
91
95
92
-
### Verify the generated documentation works
96
+
####Verify the generated documentation works
93
97
94
98
To generate the documentation you can use `mkdocs`:
95
99
@@ -110,7 +114,7 @@ point your browser to Now you can point your browser to
110
114
`.proto`](https://github.com/pseudomuto/protoc-gen-doc) files is using
111
115
`docker`.
112
116
113
-
### Initialize the GitHub pages website
117
+
####Initialize the GitHub pages website
114
118
115
119
The generated documentation can be easily published via GitHub pages, and it
116
120
will be automatically updated for new pushed and releases, but for that to work
@@ -129,7 +133,7 @@ Then make sure that GitHub pages is enabled in
129
133
If all went well, your website should be available soon via
130
134
`https://<repo-owner>.github.io//<repo-name>/`.
131
135
132
-
## Migrate an existing project
136
+
###Migrate an existing project
133
137
134
138
The easiest way to migrate an existing project is to just generate a new one
135
139
basing all the inputs in the current project metadata and then overwritting the
@@ -165,7 +169,7 @@ git commit -a
165
169
project](#create-the-local-development-environment) section to finish the
166
170
setup.
167
171
168
-
## Update an existing project
172
+
###Update an existing project
169
173
170
174
To update an existing project you can use the [Cookiecutter *replay
171
175
file*](https://cookiecutter.readthedocs.io/en/stable/advanced/replay.html) that
0 commit comments