Update examples and instructions in README

[smjoshiatglobus]

• Fixes issue Replace all references of agilepathway with SpectoLabs #64 and issue Help find GitHub action #79
• Updated all references for agilepathway with SpectoLabs
• Added latest version of HoverFly in the example
• Minor formatting fixes per markdownlint extension of VS Code

[johnboyes]

@smjoshiatglobus thanks for this PR! There is a check on the commit message style which is currently failing, so would be very grateful if you can amend the commit messages to conform to this style please, as per the contributing guide?

[smjoshiatglobus]

@smjoshiatglobus thanks for this PR! There is a check on the commit message style which is currently failing, so would be very grateful if you can amend the commit messages to conform to this style please, as per the contributing guide?

Thank you and sorry for not know about the commit message style guide. This is very helpful! I have revised the last commit message (twice). Please review and let me know if any changes are needed.

[johnboyes]

@smjoshiatglobus thanks for this PR! There is a check on the commit message style which is currently failing, so would be very grateful if you can amend the commit messages to conform to this style please, as per the contributing guide?

Thank you and sorry for not know about the commit message style guide. This is very helpful! I have revised the last commit message (twice). Please review and let me know if any changes are needed.

Thanks. One of the commit messages is ok now, but the other one ("updated example, lint fixes") needs to be amended too, please.

[smjoshiatglobus]

@smjoshiatglobus thanks for this PR! There is a check on the commit message style which is currently failing, so would be very grateful if you can amend the commit messages to conform to this style please, as per the contributing guide?

Thank you and sorry for not know about the commit message style guide. This is very helpful! I have revised the last commit message (twice). Please review and let me know if any changes are needed.

Thanks. One of the commit messages is ok now, but the other one ("updated example, lint fixes") needs to be amended too, please.

I was baffled by the same! I found out how to amend last commit message and did it. Then I realized that the check was still failing and it was probably due to subject line of the PR, which probably becomes a commit message when merging. I have fixed it now and this check seems to have passed: https://github.com/SpectoLabs/hoverfly-github-action/actions/runs/13914168231/job/38934192603?pr=80.

Is that good enough or do I need to go back and figure out how to amend older commit messages?

[johnboyes]

Is that good enough or do I need to go back and figure out how to amend older commit messages?

Nice work @smjoshiatglobus, the commit message check is passing now 🎉

The only thing preventing me from merging this now is that there are other required checks which are not running for some reason. This may be because this repo has been dormant for so long, and/or it may be because this is the first PR submitted from a fork. It's difficult for me to diagnose because I don't have admin access on this SpectoLabs org. I'll work with the admins to get to the bottom of it, but it may take a few days as I have a lot of other things on at the moment. We'll get there though, thanks for your patience.

[johnboyes]

@smjoshiatglobus being able to amend earlier Git commit messages is a handy skill to have by the way - this is a useful guide on how to do so, FYI: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

[johnboyes]

@smjoshiatglobus good news: if you can please rebase this pull request against the main branch in this SpectoLabs/hoverfly-github-action repo, and then force push your commits to your forked PR, then I think the status checks will then all pass, allowing me to go ahead and merge the PR 😎

[johnboyes]

Thanks @smjoshiatglobus, we are almost there. I've asked @marcoioco to make the final tweaks to the required status checks and then we should be good to go.

Thanks again for this PR and being patient with all the admin involved to get it merged. You've paved the way for any future PRs from external contributors like yourself to this repo to be seamless from now on 👍🏻

[smjoshiatglobus]

Thanks @smjoshiatglobus, we are almost there. I've asked @marcoioco to make the final tweaks to the required status checks and then we should be good to go.

Thanks again for this PR and being patient with all the admin involved to get it merged. You've paved the way for any future PRs from external contributors like yourself to this repo to be seamless from now on 👍🏻

Thank you for managing these repositories, showing me the path to good Git commit messages, and your kind words!