Philipp Schlarb

Yeah sure I can change it, but I would walk through it myself first to see if it works. Not sure if I can finish that before tomorrows contributors call.

Just testet the documentation with indy-cli-rs it works fine. Should the old indy-cli install be deleted from the docs in all and only reference indy-cli-rs or bundled von network?

I think the branch protection and status checks needs to be updated before merging.

Does it make sense, to incorporate that into the pipeline? https://github.com/rickstaa/action-black/

Currently the ubtunu-20.04 branches for plenum, node and sovrin token-plugin use the indy-shared-gha linting process from [here](https://github.com/hyperledger/indy-shared-gha/blob/main/.github/workflows/lint.yaml). It is currently using flake8 in with the following versions: `flake8==3.8.4` `pep8==1.7.1` `pep8-naming==0.6.1`...

Hm i think we haven't really looked into it more. And i think it is only the special case if someone wants to install mixed(apt and pypi installation) that this...

I think it is safe to say that the commits regarding the github actions (`.github/*`) can be ignored. The most work on the pipelines is already targeted to the new...

Hm one thing that comes to my mind is the documentation changes in main(espiacially the new network doc) that aren't in the ubuntu20 branch. But main wasn't compared here. Regarding...

Dev Containers are basically just docker containers with all your project related dependencies and some for vscode to attach to. You basically start it, mount your workspace and work inside...

@WadeBarnes should we close this issue, since we have a working workaround for the moment? Or should it stay open as a reminder for the rocksdb upgrades?