cupcakearmy/confluence-markdown-sync
1
0
Fork 0
mirror of https://github.com/cupcakearmy/confluence-markdown-sync.git synced 2024-12-23 00:16:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Compare commits

base: cupcakearmy:0d3d395931e4029c52c77a5f4bce894dfbbcee96
Branches Tags
cupcakearmy:master
cupcakearmy:v1.0.3
cupcakearmy:v1.0.2
cupcakearmy:v1.0.1
cupcakearmy:v1
..
compare: cupcakearmy:93af96cd42063c8cf86dbec86a9e70ca0b2a0463
Branches Tags
cupcakearmy:master
cupcakearmy:v1.0.3
cupcakearmy:v1.0.2
cupcakearmy:v1.0.1
cupcakearmy:v1

No commits in common. "0d3d395931e4029c52c77a5f4bce894dfbbcee96" and "93af96cd42063c8cf86dbec86a9e70ca0b2a0463" have entirely different histories.
0d3d395931 ... 93af96cd42

1 changed files with 1 additions and 5 deletions
Show Stats Expand all files Collapse all files

6
README.md
View File

@ -41,7 +41,7 @@ It's **higly reccomended** that you use secrets!
To use them you need them to specify them before in your repo. [Docs](https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets)
Then you can use them in any input field.
The you can use them in any input field.
```yml
# .github/workflows/my-workflow.yml
@ -49,10 +49,6 @@ Then you can use them in any input field.
token: ${{ secrets.token }}
```
## Known Limitations
For now images will not be uploaded [see ticket](https://github.com/cupcakearmy/confluence-markdown-sync/issues/5), they would require extra steps. If anyone feedls brave enough, constributions are welcomed :)
## Development
1. Clone the repo