bii publish publishes your code to biicode.
$ bii publish
Once you’ve succesfully published your code to our servers, command line prompt will show a info message about your block name user_name/block_name
and the version ID number:
INFO: Publishing block: myuser/myblock
INFO: *****************************
INFO: ***** Publishing public ****
INFO: *****************************
INFO: Successfully published myuser/myblock: 1
Tag’s default value is DEV
, but all release life-cycle tags are available:
DEV
: Code is under development.
ALPHA
: It’s usually code ready to shared with close friends or colleagues.
BETA
: Code ready for BETA testers!
STABLE
: Tested and ready to reuse.
These tags define the development state of your code.
policies.bii file holds your policies about what kind of code tags you allow for each the blocks you use.
Publish your blocks with different tags:
$ bii publish --tag STABLE
When working with a block cloned from a git repository, use bii publish -r or bii publish –remote to publish git info along with your block:
$ bii publish -r
This way your reference to the repo and commit will be saved and shown in your block header.
You can also use tags:
$ bii publish -r --tag STABLE
If there’s more than one block within your project, specify which one you want to publish:
$ bii publish USER_NAME/BLOCK_NAME
fenix
user is editing two blocks, fenix/vector
and fenix/matrix
. He wants to publish just fenix/vector using DEV tag:
$ bii publish fenix/vector
After a while, he’s sure about publishing fenix/vector
as STABLE version:
$ bii publish fenix/vector --tag STABLE
Got any doubts? Ask in our forum.