Open Source

[robinmanuelthiel]

• Add Docusaurus Docs
• Add Pipeline to publish Docs to GitHub pages
• Clean from all potentially checked-in secrets (check in GitGuardian)
• Check issues if they have any security-relevant or embarrassing information
• Short description in README
• Quick "Getting Started" in README with way to download package and init (if required)
• Link to documentation in README
• Add MIT license
• Update Release Pipelines to public NuGet/NPM feeds
• Semantic Versioning starting at v1.0.0

[robinmanuelthiel]

Blocked by #70

[SebastianKuesters]

@robinmanuelthiel there were two actions for some reason concurrent, which leads to the failing. After re-run it worked, you can continue

[robinmanuelthiel]

Don't hink its two actions. It happens again. #79

Could it be, that the tests can't be run in parallel?

[robinmanuelthiel]

@SebastianKuesters, I think I fixed it by not allowing the tests to run in parallel.

see 149e74c
and https://docs-internal.wemogy.com/general/conventions/languages/dotnet#parallelism

Anyway, although it fixes it for now, I would argue that this is a clean-code antipattern. Tests should be totally independent of each other and not rely on each other's orders or parallelism of execution. Also, I think that many test that are in the *.UnitTests projects are actually integration tests. I created an issue for cleaning the tests in the future: #81