Skip to content

Commit 56d8241

Browse files
authored
📝 added link to wiki page on argument value explanation and fixed broken img links (#11)
* 💡 Moved comments on error codes to wiki * 📝 updated pipeline console log after logic checks added * 🔖 marking version 1.0.1 after enhancements The changes were not breaking to anything useing v1.0.0 commands. This update only improves effiency * 📝 added link to wiki page on argument value explination and fixed broken img links
1 parent 9d472c0 commit 56d8241

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Let your CI Pipeline manage getting those plugin updates from your unix WordPres
1616

1717
#### Live WordPress Branch History
1818

19-
![AzureHistory](https://github.com/devnetkc/readme-assets/raw/master/Images/WordPress-commit-history.png)
19+
![AzureHistory](https://raw.githubusercontent.com/devnetkc/readme-assets/master/Images/WordPress-commit-history.png)
2020

2121
### How To Use
2222

@@ -30,6 +30,8 @@ bash ~/wp-git-sync.sh \
3030
-u $(DevOpsTokenUser)
3131
````
3232

33+
More information on the [arguments](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/How-To-Use#arguments) is available on the [WIKI](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki) page [__How to Use__](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/How-To-Use)
34+
3335
#### Azure Pipeline
3436

3537
YAML Example:
@@ -52,7 +54,7 @@ steps:
5254

5355
Classic Editor Example:
5456

55-
![PipelineScreen](https://github.com/devnetkc/readme-assets/raw/master/Images/Azure-Pipeline-Example.png)
57+
![PipelineScreen](https://raw.githubusercontent.com/devnetkc/readme-assets/master/Images/Azure-Pipeline-Example.png)
5658

5759
Console Log:
5860

@@ -92,7 +94,7 @@ Console Log:
9294

9395
---
9496

95-
Essentially, it allows WordPress developers to be more hands off with their shared hosting wordpress server backends, while still fully benefitting from any of the many source control repository and project board sites for git — but while using WordPress at the same time.
97+
Essentially, it allows WordPress developers to be more hands off with their shared hosting WordPress server backends, while still fully benefitting from any of the many source control repository and project board sites for git — but while using WordPress at the same time.
9698

9799
## Contributing
98100

0 commit comments

Comments
 (0)