Releases: ditcraft/cli
v0.3.1 - Revamped KYC process and logging
After working on this release for quite a while we are proud to present our changes. We completely revamped to KYC process to be very user-friendly and smooth. Instead of sending out a tweet and waiting for our twitter bot to catch and process it you are now able to login on the ditExplorer via GitHub or Twitter, paste your ditCLI's address and you're done 🏁
We also implemented a logging feature with a very easy and nice way to show us your logs! You can now simply can dit upload_logs and you'll receive a 10-digit code that represents your uploaded logs when you communicate with us - how cool is that?
Changelog
- Revamped KYC process with Twitter/Github Login instead of Tweet
- Included logging with comfortable upload feature
- Bug fix when voting on proposals for repositories that you haven't properly initialized
- Fixed a bug that led to false positives when checking a users git config
Found a bug?
Open an issue here!
Got feedback?
Let us know on Twitter, we love to hear from you!
v0.3 - dit is the new git
A new version 0.3 as arrived 🎉 Many hours of work and a lot of brainpower are incorporated in this release. The main focus of this release are the developers using the ditCLI - you 👨💻
You are probably used to git and you don't want to encounter strange behaviour when using the ditCLI in contrast to git. We completely reworked the way we handle the git calls and are now able to provide you with a new and polished version of the ditCLI, where everything related to git is like you would expect it to be! Just go ahead and type away - we are already waiting for you!
We also made some changes under the hood improving stability (especially of the connection to the Ethereum nodes) and usability.
Changelog
- Native git commands in dit! While we had some git commands integrated into our client, we now switched to a new method of integrating the git calls. You can now use a loooooot more git commands, try them out!
- Fallback mode for connections to Ethereum node (the client will try multiple nodes of one doesn't work or is down)
- Switch from commit-voting to master-branch voting. Now you are asked to start a vote when merging into the master branch
- One line install script
- Pre-defined knowledge labels (No confusions between "nodejs" and "Node.JS" anymore)
- Restructured config for easier access (improved the quality of the codebase)
- Improved output (no unnecessary indicator in front anymore)
Found a bug?
Open an issue here!
Got feedback?
Let us know on Twitter, we love to hear from you!
v0.2 - A new chapter
The release v0.2 includes many changes - some under the hood, some very interesting ones. We are finally live and deployed to our mainnet, the xDai chain 🎉! This release means a lot to us, since we are now one step further from just being a tech-demo to becoming something that can be used in the everyday life of each and every developer. We also put a lot of usability improvements and features into this release to really smoothen the experience for the user.
Changelog
- Deployed to the xDai chain
- Users can now switch between modes live and demo with
dit mode - More fine-granular details about a votes' outcome
- You are now warned when
dit setupwould overwrite your config - A new command
dit updatewill handle an update of the ditCLIs config after an update that would otherwise break the ditCLIs - Removed the hard-coded demo validators in favour of automated demo validators
Found a bug?
Open an issue here!
Got feedback?
Let us know on Twitter, we love to hear from you!
v0.1 - To new Adventures
It's finally here - the first version of the dit client - v0.1 🎉 This version includes a lot of upgrades that happened under the hood since the v0.1-alpha got released. But some upgrade that might be interesting for, so feel free to take a look on the changelog below!
The dit client now supports the basic workflow that is needed in order to participate in a decentralized version of git. You can commit, push, vote and finalize stuff in the end. Even if we are pretty confident, the whole client is still in alpha stage, so we suggest to take the client for a test ride with the demo mode before using it in anywhere else. Let us know what you think!
Changelog
- GitHub, Gitlab and Bitbucket repositories are now supported, if you need anything else just let us know!
- Commands in the output of the client are now colorized for better visibility
- Complete overhaul of the smart contract architecture was implemented, streamlining the whole process and further reducing gas cost. Since the single ditContracts deployments are gone, the initialization of a repo is now only at 192k gas compare to 2000k before!
- Demo-Mode is now properly implemented. Although users won't notice a difference it simplifies the code and development a lot!
Found a bug?
Open an issue here!
Got feedback?
Let us know on Twitter, we love to hear from you!
v0.1 - Alpha of the first version
v0.1 of the dit client will include the basic functionality, covering the most important parts of the dit workflow, namely: committing new changes, starting votes, voting and resolving things in the end (leading to a merge or rejection of changes). There are still some things to be implemented but this alpha already covers most of them.
The finished version v0.1 will include support for all repositories (this only only works with GitHub) and an overhauled and highly improved smartcontract architecture that the client will be interacting with. Also a lot of changes under the hood.
But for now: happy testing, expect the finished version v0.1 very soon!