DOC: "go" and "dep" unknown

[buhtz]

The section Installing and using Dockertest in the README.md show the two commands (?) go and dep.

They are not installed by default on Debian and I assume Windows also. I know both of them are not "the world". ;)

It would be nice for some of the new users if you could add a small footnote to explain what go and dep are. This would make it easier to install them.

[aeneasr]

PRs welcoemd

[buhtz]

I see contributors are not welcome to you if you answer so inpolit.

I don't have to defend my self why I don't create a PR for that. Also you don't have to defend yourself why you don't.

Take a step outside of your bubble and imagine that maybe I am one of that described users. I don't know what go and dep is and I don't have the expertise to describe it so far.

I just tried to help to improve your project. This wasn't only a support question but just a hint how you can make things better for your users.

[aeneasr]

There was no intention to offend you, the easiest way to fix things is to contribute changes when requesting them.

In general though, this library is a testing utility for writing better Go tests. If users don't have Go installed, this library won't be needed as it is a targeted use case and requires at least some knowledge of Go beforehand to be useful.

[github-actions[bot]]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️