teambit · itaymendel · Jul 16, 2021 · Jul 17, 2021 · Jul 18, 2021 · Jul 19, 2021
diff --git a/...building-with-bit/compiling-components.md → ...building-with-bit/compiling-components.md b/...building-with-bit/compiling-components.md → ...building-with-bit/compiling-components.md
diff --git a/...ilding-with-bit/component-compositions.md → ...ilding-with-bit/component-compositions.md b/...ilding-with-bit/component-compositions.md → ...ilding-with-bit/component-compositions.md
diff --git a/...building-with-bit/consuming-components.md → ...building-with-bit/consuming-components.md b/...building-with-bit/consuming-components.md → ...building-with-bit/consuming-components.md
diff --git a/.../building-with-bit/creating-components.md → .../building-with-bit/creating-components.md b/.../building-with-bit/creating-components.md → .../building-with-bit/creating-components.md
diff --git a/...ilding-with-bit/documenting-components.md → ...ilding-with-bit/documenting-components.md b/...ilding-with-bit/documenting-components.md → ...ilding-with-bit/documenting-components.md
diff --git a/docs/building-with-bit/environments.md → __archived/building-with-bit/environments.md b/docs/building-with-bit/environments.md → __archived/building-with-bit/environments.md
diff --git a/...building-with-bit/exporting-components.md → ...building-with-bit/exporting-components.md b/...building-with-bit/exporting-components.md → ...building-with-bit/exporting-components.md
diff --git a/...building-with-bit/importing-components.md → ...building-with-bit/importing-components.md b/...building-with-bit/importing-components.md → ...building-with-bit/importing-components.md
diff --git a/...uilding-with-bit/inspecting-components.md → ...uilding-with-bit/inspecting-components.md b/...uilding-with-bit/inspecting-components.md → ...uilding-with-bit/inspecting-components.md
diff --git a/...uilding-with-bit/installing-components.md → ...uilding-with-bit/installing-components.md b/...uilding-with-bit/installing-components.md → ...uilding-with-bit/installing-components.md
diff --git a/docs/building-with-bit/manage-workspace.md → ...ved/building-with-bit/manage-workspace.md b/docs/building-with-bit/manage-workspace.md → ...ved/building-with-bit/manage-workspace.md
diff --git a/...uilding-with-bit/publishing-components.md → ...uilding-with-bit/publishing-components.md b/...uilding-with-bit/publishing-components.md → ...uilding-with-bit/publishing-components.md
diff --git a/.../building-with-bit/removing-components.md → .../building-with-bit/removing-components.md b/.../building-with-bit/removing-components.md → .../building-with-bit/removing-components.md
diff --git a/docs/building-with-bit/scoping-components.md → ...d/building-with-bit/scoping-components.md b/docs/building-with-bit/scoping-components.md → ...d/building-with-bit/scoping-components.md
diff --git a/docs/building-with-bit/testing-components.md → ...d/building-with-bit/testing-components.md b/docs/building-with-bit/testing-components.md → ...d/building-with-bit/testing-components.md
diff --git a/.../building-with-bit/tracking-components.md → .../building-with-bit/tracking-components.md b/.../building-with-bit/tracking-components.md → .../building-with-bit/tracking-components.md
diff --git a/...uilding-with-bit/versioning-components.md → ...uilding-with-bit/versioning-components.md b/...uilding-with-bit/versioning-components.md → ...uilding-with-bit/versioning-components.md
@@ -54,7 +54,7 @@ bit tag --soft <component-id>
 3. Have the CI run the following command to tag all components suggested to be versioned (suggested by the previous 'soft tag')
 
 ```bash
-bit tag --persist --all
+bit tag --persist
 ```
 
 ### Untag a component

diff --git a/docs/cli/cli-reference.md → __archived/cli/cli-reference.md b/docs/cli/cli-reference.md → __archived/cli/cli-reference.md
diff --git a/...mponent-architecture/build-like-google.md → ...mponent-architecture/build-like-google.md b/...mponent-architecture/build-like-google.md → ...mponent-architecture/build-like-google.md
diff --git a/...nent-architecture/composing-components.md → ...nent-architecture/composing-components.md b/...nent-architecture/composing-components.md → ...nent-architecture/composing-components.md
diff --git a/...ponent-architecture/naming-components2.md → ...ponent-architecture/naming-components2.md b/...ponent-architecture/naming-components2.md → ...ponent-architecture/naming-components2.md
diff --git a/...ent-architecture/organizing-components.md → ...ent-architecture/organizing-components.md b/...ent-architecture/organizing-components.md → ...ent-architecture/organizing-components.md
diff --git a/...ponent-architecture/theming-components.md → ...ponent-architecture/theming-components.md b/...ponent-architecture/theming-components.md → ...ponent-architecture/theming-components.md
diff --git a/...nt-architecture/thinking-in-components.md → ...nt-architecture/thinking-in-components.md b/...nt-architecture/thinking-in-components.md → ...nt-architecture/thinking-in-components.md
diff --git a/docs/components/commands/bit-init.md → __archived/components/commands/bit-init.md b/docs/components/commands/bit-init.md → __archived/components/commands/bit-init.md
diff --git a/docs/components/commands/bit-templates.md → ...ived/components/commands/bit-templates.md b/docs/components/commands/bit-templates.md → ...ived/components/commands/bit-templates.md
diff --git a/.../components/commands/git-commit-bitmap.md → .../components/commands/git-commit-bitmap.md b/.../components/commands/git-commit-bitmap.md → .../components/commands/git-commit-bitmap.md
diff --git a/docs/components/components/bit-add.md → __archived/components/components/bit-add.md b/docs/components/components/bit-add.md → __archived/components/components/bit-add.md
diff --git a/...mponents/components/bit-create-warning.md → ...mponents/components/bit-create-warning.md b/...mponents/components/bit-create-warning.md → ...mponents/components/bit-create-warning.md
diff --git a/docs/components/components/bit-show.md → __archived/components/components/bit-show.md b/docs/components/components/bit-show.md → __archived/components/components/bit-show.md
diff --git a/docs/components/components/bitmap-example.md → ...d/components/components/bitmap-example.md b/docs/components/components/bitmap-example.md → ...d/components/components/bitmap-example.md
diff --git a/docs/components/components/namespaces.md → ...hived/components/components/namespaces.md b/docs/components/components/namespaces.md → ...hived/components/components/namespaces.md
diff --git a/docs/components/components/path.md → __archived/components/components/path.md b/docs/components/components/path.md → __archived/components/components/path.md
diff --git a/...nts/components/react/bit-create-button.md → ...nts/components/react/bit-create-button.md b/...nts/components/react/bit-create-button.md → ...nts/components/react/bit-create-button.md
diff --git a/...onents/react/bit-create-component-card.md → ...onents/react/bit-create-component-card.md b/...onents/react/bit-create-component-card.md → ...onents/react/bit-create-component-card.md
diff --git a/...s/react/bit-create-multiple-components.md → ...s/react/bit-create-multiple-components.md b/...s/react/bit-create-multiple-components.md → ...s/react/bit-create-multiple-components.md
diff --git a/...nts/components/react/test-dependencies.md → ...nts/components/react/test-dependencies.md b/...nts/components/react/test-dependencies.md → ...nts/components/react/test-dependencies.md
diff --git a/docs/components/components/styles.md → __archived/components/components/styles.md b/docs/components/components/styles.md → __archived/components/components/styles.md
diff --git a/docs/components/examples/react/button.md → ...hived/components/examples/react/button.md b/docs/components/examples/react/button.md → ...hived/components/examples/react/button.md
diff --git a/docs/components/examples/react/card.md → __archived/components/examples/react/card.md b/docs/components/examples/react/card.md → __archived/components/examples/react/card.md
diff --git a/.../components/examples/react/show-button.md → .../components/examples/react/show-button.md b/.../components/examples/react/show-button.md → .../components/examples/react/show-button.md
diff --git a/docs/components/install/bvm-intro.md → __archived/components/install/bvm-intro.md b/docs/components/install/bvm-intro.md → __archived/components/install/bvm-intro.md
diff --git a/docs/components/install/bvm-version.md → __archived/components/install/bvm-version.md b/docs/components/install/bvm-version.md → __archived/components/install/bvm-version.md
diff --git a/docs/components/install/install-bit.md → __archived/components/install/install-bit.md b/docs/components/install/install-bit.md → __archived/components/install/install-bit.md
diff --git a/.../components/install/install-bvm-errors.md → .../components/install/install-bvm-errors.md b/.../components/install/install-bvm-errors.md → .../components/install/install-bvm-errors.md
diff --git a/...omponents/install/install-bvm-solution.md → ...omponents/install/install-bvm-solution.md b/...omponents/install/install-bvm-solution.md → ...omponents/install/install-bvm-solution.md
diff --git a/docs/components/install/install-bvm.md → __archived/components/install/install-bvm.md b/docs/components/install/install-bvm.md → __archived/components/install/install-bvm.md
diff --git a/.../components/install/install-components.md → .../components/install/install-components.md b/.../components/install/install-components.md → .../components/install/install-components.md
diff --git a/docs/components/install/legacy-warning.md → ...ived/components/install/legacy-warning.md b/docs/components/install/legacy-warning.md → ...ived/components/install/legacy-warning.md
diff --git a/docs/components/install/scoped-registry.md → ...ved/components/install/scoped-registry.md b/docs/components/install/scoped-registry.md → ...ved/components/install/scoped-registry.md
diff --git a/docs/components/quick-guide.md → __archived/components/quick-guide.md b/docs/components/quick-guide.md → __archived/components/quick-guide.md
diff --git a/...nents/remote-scopes/create-bit-account.md → ...nents/remote-scopes/create-bit-account.md b/...nents/remote-scopes/create-bit-account.md → ...nents/remote-scopes/create-bit-account.md
diff --git a/...ents/remote-scopes/create-remote-scope.md → ...ents/remote-scopes/create-remote-scope.md b/...ents/remote-scopes/create-remote-scope.md → ...ents/remote-scopes/create-remote-scope.md
diff --git a/...omponents/workspace/default-scope-name.md → ...omponents/workspace/default-scope-name.md b/...omponents/workspace/default-scope-name.md → ...omponents/workspace/default-scope-name.md
diff --git a/...components/workspace/files-bit-creates.md → ...components/workspace/files-bit-creates.md b/...components/workspace/files-bit-creates.md → ...components/workspace/files-bit-creates.md
diff --git a/...components/workspace/react-environment.md → ...components/workspace/react-environment.md b/...components/workspace/react-environment.md → ...components/workspace/react-environment.md
diff --git a/.../components/workspace/reset-dev-server.md → .../components/workspace/reset-dev-server.md b/.../components/workspace/reset-dev-server.md → .../components/workspace/reset-dev-server.md
diff --git a/...mponents/workspace/starting-dev-server.md → ...mponents/workspace/starting-dev-server.md b/...mponents/workspace/starting-dev-server.md → ...mponents/workspace/starting-dev-server.md
diff --git a/docs/essentials/advantages-of-bit.md → __archived/essentials/advantages-of-bit.md b/docs/essentials/advantages-of-bit.md → __archived/essentials/advantages-of-bit.md
diff --git a/docs/essentials/bit-components.md → __archived/essentials/bit-components.md b/docs/essentials/bit-components.md → __archived/essentials/bit-components.md
diff --git a/docs/essentials/scopes.md → __archived/essentials/scopes.md b/docs/essentials/scopes.md → __archived/essentials/scopes.md
diff --git a/docs/essentials/what-is.bit.md → __archived/essentials/what-is.bit.md b/docs/essentials/what-is.bit.md → __archived/essentials/what-is.bit.md
diff --git a/docs/essentials/workspace.md → __archived/essentials/workspace.md b/docs/essentials/workspace.md → __archived/essentials/workspace.md
@@ -1,6 +1,6 @@
 ---
 id: workspace
-title: Local Workspace
+title: Workspace
 ---
 
 The Bit Workspace is a local development environment for Bit Components. The local workspace gives you a monolithic development experience for building Bit Components and reusing components built by other teams.

diff --git a/docs/extending-bit/adding-a-new-tab.md → __archived/extending-bit/adding-a-new-tab.md b/docs/extending-bit/adding-a-new-tab.md → __archived/extending-bit/adding-a-new-tab.md
diff --git a/...ending-bit/creating-a-custom-generator.md → ...ending-bit/creating-a-custom-generator.md b/...ending-bit/creating-a-custom-generator.md → ...ending-bit/creating-a-custom-generator.md
diff --git a/docs/extending-bit/mutate-webpack-config.md → ...ed/extending-bit/mutate-webpack-config.md b/docs/extending-bit/mutate-webpack-config.md → ...ed/extending-bit/mutate-webpack-config.md
diff --git a/docs/getting-started/composing-components.md → ...d/getting-started/composing-components.md b/docs/getting-started/composing-components.md → ...d/getting-started/composing-components.md
diff --git a/docs/getting-started/creating-components.mdx → ...d/getting-started/creating-components.mdx b/docs/getting-started/creating-components.mdx → ...d/getting-started/creating-components.mdx
diff --git a/docs/getting-started/exporting-components.md → ...d/getting-started/exporting-components.md b/docs/getting-started/exporting-components.md → ...d/getting-started/exporting-components.md
diff --git a/...getting-started/initializing-workspace.md → ...getting-started/initializing-workspace.md b/...getting-started/initializing-workspace.md → ...getting-started/initializing-workspace.md
@@ -4,9 +4,9 @@ title: Initializing a Workspace
 ---
 
 import FilesBitCreates from '@site/docs/components/workspace/files-bit-creates.md'
-import BitInit from '@site/docs/components/commands/bit-init.md'
-import ReactEnvironment from '@site/docs/components/workspace/react-environment.md'
-import QuickGuide from '@site/docs/components/quick-guide.md'
+import BitInit from '@site/docs/mdx-components/commands/bit-init.md'
+import ReactEnvironment from '@site/docs/mdx-components/workspace/react-environment.md'
+import QuickGuide from '@site/docs/mdx-components/quick-guide.md'
 
 In order to initialize a workspace you will need to first [install Bit](installing-bit). A Bit Workspace enables you to author and manage multiple independent components in a simple and elegant way. Bit works with Git so you can either add init a new git repo or add Bit to an existing git repo.
 

diff --git a/docs/getting-started/installing-bit.md → __archived/getting-started/installing-bit.md b/docs/getting-started/installing-bit.md → __archived/getting-started/installing-bit.md
@@ -87,4 +87,4 @@ bvm upgrade
 
 ## What's next?
 
-Once you have installed Bit and BVM you can then [initialize a workspace](/getting-started/initializing-workspace) so you can manage your components.
+Once you have installed Bit and BVM you can then [create a workspace](/getting-started/initializing-workspace) to compose and ship your first components.
diff --git a/.../getting-started/installing-components.md → .../getting-started/installing-components.md b/.../getting-started/installing-components.md → .../getting-started/installing-components.md
diff --git a/docs/getting-started/remote-scope.md → __archived/getting-started/remote-scope.md b/docs/getting-started/remote-scope.md → __archived/getting-started/remote-scope.md
diff --git a/docs/getting-started/whats-next.md → __archived/getting-started/whats-next.md b/docs/getting-started/whats-next.md → __archived/getting-started/whats-next.md
diff --git a/docs/getting-started/workspace-ui.md → __archived/getting-started/workspace-ui.md b/docs/getting-started/workspace-ui.md → __archived/getting-started/workspace-ui.md
diff --git a/__archived/reference/ci-cd.md b/__archived/reference/ci-cd.md
@@ -0,0 +1,306 @@
+---
+id: ci-cd
+title: CI/CD and Deployment
+---
+
+Use your CI/CD tool to install Bit components on consuming apps or publish component automatically to [bit.dev](https://bit.dev) or any remote Bit scope.
+
+- If you want to only install components on the CI using NPM or Yarn, follow the steps bellow to [get a token](#get-a-bit-token), and [configure .npmrc on CI](#configure-npmrc-on-ci). [Go here](#common-errors) for information on common errors.
+- If you want to version and export components, first [get a token](#get-a-bit-token) and [follow these steps](#version-and-export-components-on-ci).
+
+## Get a Bit token
+
+The first thing to do is get a Bit token that has access to scopes.  
+You can create a dedicated user such as `dev@company.com` for the deployment, or use an existing user's token.
+
+> If you are using an existing user's token, follow the steps described [here](/bit-dot-dev/authentication#additional-tokens) to generate a token that does not expire on local logins.
+
+To get your token run the following command:
+
+```shell
+bit config get user.token
+```
+
+Set `user.token` as an environment parameter on your server named `BIT_TOKEN`.
+
+## Install Components on CI
+
+### Configure npmrc on CI
+
+Bit components are stored on the bit registry located in `https://node.bit.dev`.
+
+When installing components with npm or yarn, they will try to install the components starting with `@<account-name>` by resolving the `@<account-name>` registry. This configuration is stored in an `.npmrc` configuration file. Npm and yarn respect the following file locations:
+
+- per-project config file (`/path/to/my/project/.npmrc`)
+- per-user config file (`~/.npmrc`)
+- global config file (`$PREFIX/etc/npmrc`)
+- npm builtin config file (`/path/to/npm/npmrc`)
+
+When working locally, `bit login` configures this file automatically for you. You will need to set this file manually for your CI. If not done right you will get these errors:
+
+**NPM**
+
+```shell
+failed running npm install at /Users/user/devenv/example-npm-error/components/utils/string/pad-left
+npm ERR! code E404
+npm ERR! 404 Not Found: @bit/bit.utils.string.pad-left@0.0.1
+```
+
+**Yarn**
+
+```shell
+failed running yarn install at /Users/user/devenv/example-npm-error/components/utils/string/pad-left
+error An unexpected error occurred: "https://registry.yarnpkg.com/@bit%2fbit.utils.string.pad-left: Not found".
+```
+
+The error is solved by making sure that one of the `.npmrc` files has the configuration prior to running npm install. The solutions vary per vendor (see below), but the main methods are:
+
+- Define `.npmrc` in the project.
+- Generate `.npmrc` file for the CI user
+- Extend `.npmrc` configuration with vendor's tools
+
+### Manually create npmrc file
+
+You can add a `.npmrc` in your project with the following:
+
+```shell
+@<account-name>:registry=https://node.bit.dev
+@teambit:registry=https://node.bit.dev
+//node.bit.dev/:_authToken=${BIT_TOKEN}
+always-auth=true
+```
+
+Define `BIT_TOKEN` as a secret global variable on the server.
+
+### Generate `.npmrc` on server
+
+To generate the file dynamically, you need to run the following script (e.g. create a `bit_npm.sh` script):
+
+```shell
+echo "Adding bit.dev to npm registry"
+echo "always-auth=true" >> ~/.npmrc
+echo "@<account-name>:registry=https://node.bit.dev" >> ~/.npmrc
+echo "@teambit:registry=https://node.bit.dev" >> ~/.npmrc
+echo "//node.bit.dev/:_authToken={$BIT_TOKEN}" >> ~/.npmrc
+echo "Completed adding bit.dev to npm registry"
+```
+
+### Netlify
+
+On Netlify, [you cannot generate the file dynamically](https://community.netlify.com/t/common-issue-using-private-npm-modules-on-netlify/795/11), and you should [add `.npmrc` file in your project](#define-npmrc-in-the-project).
+
+Add the BIT_TOKEN as [environment variable](https://www.netlify.com/docs/continuous-deployment/#environment-variables)
+
+### ZEIT Now
+
+On ZEIT Now, use the `now.json` configuration file to add an [environment variable](https://zeit.co/docs/v2/build-step#using-environment-variables-and-secrets) containing the contents of your `~/.npmrc` file.
+
+First, add the following to `now.json`:
+
+```json
+{
+  "name": "my-app",
+  "version": 2,
+  "build": {
+    "env": {
+      "NPM_RC": "@my-app-npmrc"
+    }
+  }
+}
+```
+
+Then, create a secret with the contents of your `~/.npmrc`.
+
+```shell
+now secrets add my-app-npmrc "$(cat ~/.npmrc)"
+```
+
+Note that `my-app-npmrc` is the name of the secret and can be named anything you wish.
+
+### Gitlab
+
+In `.gitlab-ci.yml` run the script that [generates the file for the user](#generate-npmrc-on-server) as an initial step before running npm install.
+
+Add the BIT_TOKEN as an [environment variable](https://docs.gitlab.com/ee/ci/variables/)
+
+### GitHub actions
+
+Add the BIT_TOKEN as a [secret](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) in GitHub.
+
+In the GitHub workflow file, create a step before the npm install section:
+
+```shell
+- name: init bit.dev
+  run: |
+    echo "Adding bit.dev to npm registry"
+    npm config set @bit:registry https://node.bit.dev
+    npm config set @<account-name>:registry=https://node.bit.dev
+    npm config set @teambit:registry=https://node.bit.dev
+    npm config set //node.bit.dev/:_authToken ${BIT_TOKEN}
+    echo "Completed adding bit.dev to npm registry"
+  env:
+    BIT_TOKEN: ${{ secrets.BIT_TOKEN }}
+```
+
+### Heroku
+
+To generate the `.npmrc` before installing dependencies, run a pre-build script as described [here](https://devcenter.heroku.com/articles/nodejs-support#heroku-specific-build-steps).
+
+Add the `BIT_TOKEN` as an [environment variable](https://devcenter.heroku.com/articles/config-vars#managing-config-vars)
+
+### Azure pipelines
+
+Use the [npm authenticate task](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/npm-authenticate?view=azure-devops) to setup the `.npmrc` configuration in your pipeline.
+
+### Common Errors
+
+#### 'package not found' (404) when importing a component
+
+NPM or Yarn throws 'package not found' when importing a component. This is likely because the component has a dependency on a @bit component. Make sure [npmrc is configured](#bit-installed-components).
+
+#### Unauthorized (401) when installing a component
+
+Possible reasons:
+
+- npmrc is not properly [configured](#bit-installed-components)
+- You do not have the right permissions on the Collection that the components are hosted in, and are therefore unable to access its components. Make sure you have at least read permissions for the collection that host the components.
+- Yarn does not send an authentication token when installing packages from a `yarn.lock` file. This is a [known issue](https://github.com/yarnpkg/yarn/issues/4451). Make sure `always-auth` is [configured in `.npmrc`](#bit-installed-components).
+
+## Version and Export Components on CI
+
+### Install and configure Bit
+
+Follow the instructions in [bit docker readme](https://github.com/teambit/bit/blob/master/scripts/docker-teambit-bit) to get a docker with bit installed.
+
+To configure bit on the server, you need to run the following commands:
+
+```shell
+bit config set user.token ${BIT_TOKEN}
+```
+
+### Versioning and Publishing
+
+The flow for versioning and publishing components work as follows:
+
+1. On your local computer run `bit tag` with the `--soft` option to annotate that modified components should be versioned and exported.
+1. Bit updates `.bitmap` with information on new versions to publish.
+1. Collaborate with your peers on the soon-to-be published components, their semantic version and changelog messages.
+1. Merge changes to main branch.
+1. CI/CD versions all marked components and publish them.
+1. CI/CD commits back to the repository the updated `.bitmap` without annotations on versions to be exported.
+
+> **Where is the 'test' and 'build'?**
+>
+> The `tag` command runs the 'build pipeline' before versioning a component. This pipeline includes building and testing. if any of these tasks fails, the versioning process will be aborted.
+
+:::info use soft tags in local workspaces
+Components in local workspaces should be 'soft-tagged'.
+That means they are registered in the `.bitmap` file as pending to be versioned, but not yet versioned.
+The versioning process should only happen in the CI (once changes to the workspace are pushed to the remote repository).
+This enables collaboration on components before they are tagged and exported.  
+[**Learn more**](/building-with-bit/exporting-components).
+:::
+
+### Using GitHub Actions
+
+> You can also follow along with this [example project.](https://github.com/teambit/harmony-with-github-actions)
+
+1. Create a new [secret variable](https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets) in your Github repository. Name it `BIT_TOKEN` and set the value of it to the `user.token` value.
+1. Create a new `tag-and-export.yml` file in your remote repository `./.github/workflows` directory.
+1. Create your script.
+
+Here's a demo script you can start with:
+
+```yaml
+# This workflow hard-tags and exports soft-tagged components
+name: Tag and Export Components
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  tag-and-export:
+    runs-on: ubuntu-latest
+    if: "!contains(github.event.head_commit.message, '--skip-ci')"
+    env:
+      BIT_TOKEN: ${{ secrets.BIT_TOKEN }}
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js 12
+        uses: actions/setup-node@v1
+        with:
+          node-version: 12.x
+      - name: Install Bit Version Manager
+        run: npm i -g @teambit/bvm
+      - name: Install latest Bit version
+        run: bvm install
+      - name: add bvm bin folder to path
+        run: echo "$HOME/bin" >> $GITHUB_PATH
+      - name: Set up bit config
+        run: |
+          bit config set analytics_reporting false
+          bit config set anonymous_reporting false
+          bit config set user.token $BIT_TOKEN
+      - name: Install packages using bit
+        run: bit install
+      - name: Hard-tag pending components
+        run: bit tag --persist
+      - name: Export components
+        run: bit export
+      - name: Commit changes made to .bitmap
+        run: |
+          git config --global user.name '${{ github.actor }}'
+          git config --global user.email '${{ github.actor }}@users.noreply.github.com'
+          git add .bitmap
+          git commit -m "update .bitmap with new component versions (automated). --skip-ci"
+          git push
+```
+
+### Using GitLab CI
+
+1. Generate a Personal Access Token with "Read Repository" and "Write Repository" permissions (this will be `GL_TOKEN`).
+1. Generate `BIT_TOKEN` by grabbing it from your local "bit config" output.
+1. Configure both tokens as project variables for your GitLab project and name them `GL_TOKEN` and `BIT_USER_TOKEN`.
+1. Create a `.gitlab-ci.yml` file in the root of the repository.
+1. Create your script.
+
+Here's a demo script you can start with:
+
+```yml
+publish_components:
+  image: node:latest
+  only: master
+  script:
+    # Install Bit and configure permissions
+    - npm i -g @teambit/bvm
+    - bvm install
+    - export PATH=$HOME/bin:$PATH
+    - bit config set analytics_reporting false
+    - bit config set anonymous_reporting false
+    - bit config set user.token $BIT_TOKEN
+    # Install dependencies
+    - bit install
+    # Version all pending components
+    - bit tag --persist
+    # Export components
+    - bit export
+    # Setup Git and commit back .bitmap changes
+    - git config --global user.email "some@email.address"
+    - git config --global user.name "some ci account"
+    - export GL_RELEASE_GITLAB_API_TOKEN=$GL_TOKEN
+    # This checkout is a workaround for the "error: src refspec master does not match any." error
+    - git checkout master
+    # Add the modified ".bitmap" file
+    - git add .
+    # Replace origin with authenticated origin
+    - git remote rm origin
+    - git remote add origin https://[repo-owner]:$GL_RELEASE_GITLAB_API_TOKEN@gitlab.com/[repo-ower]/[repo-name].git
+    # Using [skip ci] as its a feature for GitLab that will not trigger CI for this commit
+    - git commit -am 'publish components [skip ci]'
+    - git pull origin master
+    - git push origin master
+```
Original file line number	Diff line number	Diff line change
Expand Up		@@ -87,4 +87,4 @@ bvm upgrade

		## What's next?

		Once you have installed Bit and BVM you can then [initialize a workspace](/getting-started/initializing-workspace) so you can manage your components.
		Once you have installed Bit and BVM you can then [create a workspace](/getting-started/initializing-workspace) to compose and ship your first components.