Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update readme format #60

Closed
stevanlohja opened this issue Oct 15, 2019 · 1 comment
Closed

Update readme format #60

stevanlohja opened this issue Oct 15, 2019 · 1 comment
Assignees
@stevanlohja
Labels
documentation Improvements or additions to documentation released

Comments

@stevanlohja
Copy link
Contributor

Update readme format to be on par with https://github.com/etclabscore/jade-service-runner
@stevanlohja stevanlohja added the documentation Improvements or additions to documentation label Oct 15, 2019
@stevanlohja stevanlohja self-assigned this Oct 15, 2019
stevanlohja added a commit that referenced this issue Oct 25, 2019
@stevanlohja
Merge pull request #76 from stevanlohja/master
1bea204 
fix: restructued readme content, this fixes #60
shanejonas pushed a commit that referenced this issue Feb 12, 2020
@semantic-release-bot
chore(release): 1.1.3 [skip ci]
92de24d 
## [1.1.3](1.1.2...1.1.3) (2020-02-12)

### Bug Fixes

* change RUN IT img to link to release, fixes [#78](#78) ([cb64b51](cb64b51))
* restructued readme content, this fixes [#60](#60) ([7c0b98d](7c0b98d))
* **README:** away > way typo ([f8d65b2](f8d65b2))
* update jade service runner to latest ([0463a18](0463a18))
* updated img src for ui img ([ea5e327](ea5e327))
@shanejonas
Copy link
Contributor

🎉 This issue has been resolved in version 1.1.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stevanlohja stevanlohja

Labels
documentation Improvements or additions to documentation released
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shanejonas @stevanlohja