GitHub and Bitbucket are notorious Git (Bitbucket works with Mercurial too) repository web-based hosting service which offers the distributed revision control and source code management (SCM) functionality of Git as well as add their own features.
Biicode does not intend to be version control system. We recommend you using a control version system so you can keep your code safe and versioned. You can use also SVN or CVS.
init the git repository in your block folder. As in the example:
$ bii init my_block -L $ cd my_block $ git init . $ git add . $ git commit -m "my very first commit"
You can also add a remote repository:
$ git remote add origin https://github.com/user/repo.git
Put your code into a biicode block, as usual:
~$ git clone https://Your_Repo_URL.git ~$ cd your_repository ~/your_repository$ bii init -L
And follow this guide to adapt your library to biicode.
The biicode satus badge is a dynamically generated image displaying your block’s latest published version in biicode.
This badge lets developers know your code is available to reuse at biicode. It is something determinant in the use of a dependency manager and you can place it in the readme files of your VCS repository and in the biicode block.
Let people know your code can be reused easily!
bii publish -r or
bii publish --remote uses the git info within your block to publish it to biicode along with your block. This way everyone knows “who is” the git repo mantaining the biicode block and the specific commit creating each block version.
$ bii publish -r
This is how publishing with
bii publish --remote looks like:
bii publishparameters, for example:
bii publish -r --tag STABLE --versiontag v1.0.2