Make your CI/CD pipeline immutable by leveraging the power of IdeaBlock to automatically tether git commits to the Bitcoin and Litecoin blockchains.
So what does IdeaBlock Commit do, exactly? Every time a user makes a commit to a local git repository in which IdeaBlock Commit is initialized, it does the following:
> npm i -g ideablock-commit
> git clone https://github.com/ideablock/commit.git > cd commit > npm i -g
> wget https://ideablock.io/ideablock-commit-latest.tgz > tar -xzvf ideablock-commit-latest.tgz > npm i -g
Initialization From any root directory of a git repo, run the following to initialize automatic git commit blockchain tethering in that repository:
> ideablock-commit init
Turn Off (Pause) Again, in a git repository root directory, turn off (pause) automatic commit tethering in that repository by using the off or pause command:
> ideablock-commit off > ideablock-commit pause
Turn On (Resume) Resume automatic commit tethering in a repository where this functionality is presently paused by using the on or resume command:
> ideablock-commit on > ideablock-commit resume
Status Not sure if automatic blockchain tethering is on or off before you commit your code? You can print this information to the terminal by calling the status command at any time:
> ideablock-commit status
Remove You can completely remove IdeaBlock Commit functionality from your repository at any time by calling the remove command. If you would like to add it again later, just call the init function in the root directory of the repository at that time. The following commands are identical.
> ideablock-commit remove > ideablock-commit uninstall
Important Information: The current version is an initial release of IdeaBlock Commit and should be considered very beta. Its functionality has been tested by our team - but please be aware that this is not production-ready software. Please feel free to submit pull requests to add features or to let us know about any issues at the IdeaBlock Commit source page on GitHub. You can also find the package on npm and yarn.
It is very important to remember that IdeaBlock never receives the actual files that form the substance of the repository you protect with IdeaBlock Commit - they stay with you, locally. It is therefore incumbent on every user to practice good operational security and ensure that a redundancy plan is in place when it comes to the files stored in your ~/.ideablock/commits directory.
By only sending IdeaBlock the hashes associated with your repositories, you are even protecting yourself against any future argument that you disclosed a trade secret to a third party - namely, us!
Thank you for your interest in IdeaBlock Commit and the rest of our early software tools, which include IdeaBlock Beta and IdeaBlock CLI with more coming soon! We appreciate your help and feedback - they are key in making our offerings as robust and bug-free as possible!