chore: merge branch 'dev' into v3-next

Author: woothu

CONTRIBUTING.md renamed to .github/CONTRIBUTING.md

@@ -36,7 +36,7 @@ Guidelines for bug reports:
 
 1. **Use the GitHub issue search** — check if the issue has already been reported.
 
-2. **Check if the issue has been fixed** — try to reproduce it using the latest `master` or development branch in the repository.
+2. **Check if the issue has been fixed** — try to reproduce it using the latest `master` or `dev` branch in the repository.
 
 3. **Isolate the problem** — ideally create a [reduced test case](https://css-tricks.com/reduced-test-cases/) and a live example. [This JS Bin](http://jsbin.com/lefey/1/edit?html,output) is a helpful template.
 
@@ -101,11 +101,11 @@ included in the project:
 2. If you cloned a while ago, get the latest changes from upstream:
 
    ```bash
-   git checkout master
-   git pull upstream master
+   git checkout dev
+   git pull upstream dev
    ```
 
-3. Create a new topic branch (off the main project development branch) to
+3. Create a new topic branch (off the development branch "dev") to
    contain your feature, change, or fix:
 
    ```bash
@@ -121,7 +121,7 @@ included in the project:
 5. Locally merge (or rebase) the upstream development branch into your topic branch:
 
    ```bash
-   git pull [--rebase] upstream master
+   git pull [--rebase] upstream dev
    ```
 
 6. Push your topic branch up to your fork:
@@ -130,7 +130,7 @@ included in the project:
    git push origin <topic-branch-name>
    ```
 
-7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description against the `master` branch.
+7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description into the `dev` branch.
 
 **IMPORTANT**: By submitting a patch, you agree to allow the project owners to license your work under the terms of the [MIT License](LICENSE).
 
@@ -144,7 +144,7 @@ Inspired by Sparkbox's awesome article on [semantic commit messages](http://sees
 - fix (bug fix) -> ```git commit -m 'fix: commit-message-here'```
 - refactor (refactoring production code) -> ```git commit -m 'refactor: commit-message-here'```
 - style (formatting, missing semi colons, etc; no code change) -> ```git commit -m 'style: commit-message-here'```
-- test (adding missing tests, refactoring tests; no production code change) -> ```git test -m 'refactor: commit-message-here'```
+- test (adding missing tests, refactoring tests; no production code change) -> ```git commit -m 'test: commit-message-here'```
 
 ## Code guidelines
 

ISSUE_TEMPLATE.md renamed to .github/ISSUE_TEMPLATE.md

@@ -0,0 +1,49 @@
+name: Daily project check
+
+on:
+  schedule:
+    # build runs everyday at 6AM UTC
+    - cron: '0 6 * * *'
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [8.x, 10.x, 12.x]
+        os: [ubuntu-latest, windows-latest, macOS-latest]
+
+    steps:
+    - uses: actions/checkout@v1
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v1
+      with:
+        node-version: ${{ matrix.node-version }}
+    - name: project check
+      run: |
+        npm i
+        npm run clearCache
+        npm run build
+        npm run lint
+        npm run test:unit
+      env:
+        CI: true
+
+  e2e-chrome:
+
+    runs-on: windows-latest
+
+    steps:
+    - uses: actions/checkout@v1
+    - name: Use Node.js 12
+      uses: actions/setup-node@v1
+      with:
+        node-version: 12
+    - name: e2e chrome test
+      run: |
+        npm i
+        npm run test:e2e
+      env:
+        BROWSER: chrome

.github/workflows/daily-project-check.yml

@@ -0,0 +1,48 @@
+name: Project check
+
+on: 
+  push:
+  pull_request:
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [8.x, 10.x, 12.x]
+        os: [ubuntu-latest, windows-latest, macOS-latest]
+
+    steps:
+    - uses: actions/checkout@v1
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v1
+      with:
+        node-version: ${{ matrix.node-version }}
+    - name: project check
+      run: |
+        npm i
+        npm run clearCache
+        npm run build
+        npm run lint
+        npm run test:unit
+      env:
+        CI: true
+
+  e2e-chrome:
+
+    runs-on: windows-latest
+
+    steps:
+    - uses: actions/checkout@v1
+    - name: Use Node.js 12
+      uses: actions/setup-node@v1
+      with:
+        node-version: 12
+    - name: e2e chrome test
+      run: |
+        npm i
+        npm run test:e2e
+      env:
+        BROWSER: chrome

.github/workflows/project-check.yml

@@ -3,8 +3,7 @@
 [![Tweet](https://img.shields.io/twitter/url/http/shields.io.svg?style=social)](https://twitter.com/intent/tweet?text=CoreUI%20-%20Free%20Vue%20Admin%20Template%20&url=http://coreui.io/vue/&hashtags=bootstrap,admin,template,dashboard,panel,free,angular,react,vue)
 [![NPM][npm-coreui-vue-badge-latest]][npm-coreui-vue]
 [![Downloads](https://img.shields.io/npm/dm/@coreui/vue.svg?style=flat-square)][coreui]
-[![Jest](https://img.shields.io/badge/Jest-^24.9.0-blue.svg?style=flat-square)][coreui]
-[![Vue](https://img.shields.io/badge/Vue-^2.6.10-brightgreen.svg?style=flat-square)][coreui]
+[![Vue](https://img.shields.io/badge/Vue-^2.6.11-brightgreen.svg?style=flat-square)][coreui]
 
 [npm-coreui-vue]: https://www.npmjs.com/package/@coreui/vue
 [npm-coreui-vue-badge-latest]: https://img.shields.io/npm/v/@coreui/vue/latest?style=flat-square&color=brightgreen  
@@ -97,7 +96,7 @@ Have a bug or a feature request? [Please open a new issue](https://github.com/co
 
 ### Contributing
 
-Please read through our [contributing guidelines](https://github.com/coreui/coreui-free-vue-admin-template/blob/v3-next/CONTRIBUTING.md). Included are directions for opening issues, coding standards, and notes on development.
+Please read through our [contributing guidelines](https://github.com/coreui/coreui-free-vue-admin-template/blob/v3-next/.github/CONTRIBUTING.md). Included are directions for opening issues, coding standards, and notes on development.
 
 ### Versioning
 
@@ -146,7 +145,7 @@ Some of projects created by community but not maintained by CoreUI team.
 
 ## Copyright and license
 
-Copyright 2019 creativeLabs Łukasz Holeczek. Code released under [the MIT license](https://github.com/coreui/coreui-free-vue-admin-template/blob/master/LICENSE).
+Copyright 2020 creativeLabs Łukasz Holeczek. Code released under [the MIT license](https://github.com/coreui/coreui-free-vue-admin-template/blob/master/LICENSE).
 There is only one limitation - you cannot re-distribute the `CoreUI` as stock nor if you modify the `CoreUI`. In the past we faced some problems with persons who tried to sell `CoreUI` based templates.
 
 ## Support CoreUI Development

README.md

@@ -1,5 +1,11 @@
 module.exports = {
   presets: [
-    ['@babel/preset-env']
+    [
+      '@babel/preset-env',
+      {
+        useBuiltIns: 'entry',
+        corejs: 3
+      }
+    ]
   ]
 }