Skip to content

Commit 21b7b2b

Browse files
authored
fix sub-headings
1 parent 8d35280 commit 21b7b2b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

setup-py-project.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## 1. Add GitHub workflow
1+
### 1. Add GitHub workflow
22
The workflow [file](https://github.com/Flow-Launcher/plugin-samples/blob/master/HelloWorldPython/.github/workflows/Publish%20Release.yml) will help build and deploy your project, it does the following things:
33
1. `workflow_dispatch:` gives you the option to manually run your workflow from the Actions section of your project
44
2. On pushes to main, it will kick off the workflow but ignore the push if it's only changes made to the workflow file.
@@ -34,7 +34,7 @@ push:
3434
zip -r <NAME-OF-YOUR-PLUGIN>.zip . -x '*.git*'
3535
```
3636

37-
## 2. Publish as zip
37+
### 2. Publish as zip
3838
The final step to the workflow file is this publish section, which will publish the zip file you generated, upload to GitHub Releases page and tag with the version generated from the previous step from your plugin.json file. Remmember again to replace '<NAME-OF-YOUR-PLUGIN>' with the name of your plugin.
3939
```yml
4040
- name: Publish
@@ -49,7 +49,7 @@ The final step to the workflow file is this publish section, which will publish
4949

5050
Feel free to also have a read of this [blog post](https://blog.ipswitch.com/how-to-build-your-first-github-actions-workflow) which does a simple explaination of how to use GitHub Actions Workflow.
5151

52-
## 3. Use lib directory
52+
### 3. Use lib directory
5353
Once the lib folder is included in your zip release, it can then be used without needing the user to manually pip install. You just have to tell during runtime to find those modules in your local lib folder. Do this by using this exact copy of the following block of code:
5454
```python
5555
import sys,os

0 commit comments

Comments
 (0)