You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, I'd like to commend you on the recent release of your open-source wallet. This initiative is a significant step towards transparency and fosters community involvement, which is commendable.
As a developer interested in contributing to the project, I encountered challenges setting up and running the wallet locally due to the absence of developer documentation. Would it be possible for the team to provide some insights or guidelines on how to develop locally, properly?
Furthermore, implementing GitHub Actions with basic CI tooling would be beneficial. Automating the testing process can enhance code quality and streamline contributions for the community. While I understand GitHub might not be your primary platform, given the security audit I've read, integrating some tooling here could still be advantageous.
The text was updated successfully, but these errors were encountered:
Thanks @studna, due to time constraints we weren't able to include the necessary build files and developer documentation. Will keep this issue open and provide an update when we are able to get to this task.
Documentation has been updated to include contribution guidelines. We will be exposing our internal testing on github in the near future. Leaving this issue open until we migrate it over.
Firstly, I'd like to commend you on the recent release of your open-source wallet. This initiative is a significant step towards transparency and fosters community involvement, which is commendable.
As a developer interested in contributing to the project, I encountered challenges setting up and running the wallet locally due to the absence of developer documentation. Would it be possible for the team to provide some insights or guidelines on how to develop locally, properly?
Furthermore, implementing GitHub Actions with basic CI tooling would be beneficial. Automating the testing process can enhance code quality and streamline contributions for the community. While I understand GitHub might not be your primary platform, given the security audit I've read, integrating some tooling here could still be advantageous.
The text was updated successfully, but these errors were encountered: