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
Copy file name to clipboardExpand all lines: README.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ or use the [VSCode Test Explorer](https://code.visualstudio.com/docs/python/test
60
60
61
61
### [Optional] Invoking the dev code from command line
62
62
63
-
If you installed the module in develop mode you can use it directly as seen in the instructions above. You can also use the module reference, as seen bellow.
63
+
If you installed the module in develop mode you can use it directly as seen in the instructions above. You can also use the module reference, as seen bellow.
64
64
65
65
To export a custom vision project to an Azure storage account use the following:
66
66
@@ -137,7 +137,13 @@ git tag -d v0.1.0
137
137
138
138
> Note: You will not be able to push the same version to the test Pypi instance. As a work around you can increase the prerelease 4th digit e.g. 0.1.0.1.
139
139
140
-
When you are ready push changes to remote and let github actions publish the package to the production Pypi.
140
+
When you are ready push changes to remote and let github actions publish the package to the production Pypi. Just push the tag to GitHub and the CD action will create the release:
141
+
142
+
```bash
143
+
git push origin --tags
144
+
```
145
+
146
+
> Note that currently the CD process is kicked when you push the tag and it doesn't do the CI part. So make sure your code is passing the CI part before tagging and pushing the tag to GitHub.
0 commit comments