Merge branch 'next' into tooltip-access-next

Author: Akshat55

.github/CONTRIBUTING.md

@@ -10,6 +10,7 @@ Want to contribute to this repository? Please read below first:
 * [Coding Standards](#coding-standards)
 * [Commit Message Guidelines](#commit-message-guidlines)
 * [Testing](#testing)
+* [Legal](#legal)
 
 ## IBMers Contributing
 
@@ -90,7 +91,7 @@ If your issue appears to be a bug, and hasn't been reported, open a new issue. H
 6. Commit your changes using a descriptive commit message.
 
    ```
-   $ git commit -a -m "chore: Update header with newest designs, resolves #123"
+   $ git commit -a -m -s "chore: Update header with newest designs, resolves #123"
    ```
 
    **Note:** the optional commit -a command line option will automatically "add" and "rm" edited files. See [Close a commit via commit message](https://help.github.com/articles/closing-issues-via-commit-messages/) and [writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages) for more details on commit messages.
@@ -158,3 +159,38 @@ Test your changes by running our test commands:
   ```
   npm run test:watch
   ```
+
+## Legal
+
+Each source file must include a license header for the Apache
+Software License 2.0. Using the SPDX format is the simplest approach.
+For example:
+
+```javascript
+/*
+Copyright <holder> All Rights Reserved.
+SPDX-License-Identifier: Apache-2.0
+*/
+```
+
+We have tried to make it as easy as possible to make contributions. This
+applies to how we handle the legal aspects of contribution. We use the
+same approach - the [Developer's Certificate of Origin 1.1 (DCO)][DCO] - that the Linux® Kernel [community](https://elinux.org/Developer_Certificate_Of_Origin)
+uses to manage code contributions.
+
+We simply ask that when submitting a patch for review, the developer
+must include a sign-off statement in the commit message.
+
+Here is an example Signed-off-by line, which indicates that the
+submitter accepts the DCO:
+
+```text
+Signed-off-by: John Doe <[email protected]>
+```
+
+You can include this automatically when you commit a change to your
+local git repository using the following command:
+
+```bash
+git commit -s
+```

.github/workflows/check-build.yml

@@ -2,9 +2,9 @@ name: Check build
 
 on:
   push:
-    branches: [ master ]
+    branches: [ master, next ]
   pull_request:
-    branches: [ master ]
+    branches: [ master, next ]
 
 jobs:
   build:
@@ -41,7 +41,7 @@ jobs:
 
     strategy:
       matrix:
-        angular-version: [7, 8, 9, 10, 11, 12, 13, 14]
+        angular-version: [12, 13, 14]
         node-version: [14.x]
 
     steps:

.github/workflows/dco.yml

@@ -0,0 +1,37 @@
+name: 'DCO Assistant'
+on:
+  issue_comment:
+    types: [created]
+  pull_request_target:
+    types: [opened, closed, synchronize]
+
+jobs:
+  DCO:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'DCO Assistant'
+        if:
+          (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the
+          DCO document and I hereby sign the DCO.') || github.event_name == 'pull_request_target'
+        uses: cla-assistant/[email protected]
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PERSONAL_ACCESS_TOKEN: ${{ secrets.CARBON_BOT_DCO }}
+        with:
+          path-to-signatures: 'dco-signatures.json'
+          path-to-document: 'https://github.com/carbon-design-system/carbon-dco/blob/main/dco.md'
+          branch: 'main'
+          allowlist: bot*
+          remote-organization-name: carbon-design-system
+          remote-repository-name: carbon-dco
+          create-file-commit-message: 'chore: create file to store dco signatures'
+          signed-commit-message: 'chore: $contributorName has signed the dco in #$pullRequestNo'
+          custom-notsigned-prcomment:
+            'Thanks for your submission! We ask that $you sign our [Developer Certificate of
+            Origin](https://github.com/carbon-design-system/carbon-dco/blob/main/dco.md) before we
+            can accept your contribution. You can sign the DCO by adding a comment below using this
+            text:'
+          custom-pr-sign-comment: 'I have read the DCO document and I hereby sign the DCO.'
+          custom-allsigned-prcomment: 'All contributors have signed the DCO.'
+          lock-pullrequest-aftermerge: false
+          use-dco-flag: true

.github/workflows/publish.yml

@@ -0,0 +1,50 @@
+name: Deploy
+
+on:
+  # Runs on pushes targeting release branches
+  push:
+    branches: ["master", "next", "v3", "v9"]
+
+  # Allows us to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  # Single deploy job since we're just deploying
+  publish:
+    environment:
+      name: Deploy
+    runs-on: ubuntu-latest
+    steps:
+      # Checkout to branch
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      # Set up node to use v14
+      - name: Setup Node
+        uses: actions/setup-node@v3
+        with:
+          node-version: "14"
+          cache: "npm"
+          cache-dependency-path: "package-lock.json"
+
+      - name: Install packages
+        run: npm i
+
+      # Build CCA package
+      - name: Build package
+        run: npm run build
+
+      # Run Semantic release to publish package to NPM
+      - name: Publish package
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npm run semantic-release
+
+      # Push storybook build to gh-pages branch if pushed to `master` branch
+      - name: Serve storybook
+        if: github.ref_name == 'master'
+        env:
+          GH_TOKEN: ${{ secrets.CARBON_BOT_DCO }}
+        run: ./scripts/deploy.sh
+        shell: bash

CODEOWNERS

@@ -1 +1 @@
-* @IBM/carbon-angular
+* @carbon-design-system/angular-maintainers