Начало Каталог Помощ
Вход
wangwei
/
ant-vue-admin
1
0
Разклонения 0
Файлове Задачи 0 Заявки за сливане 0 Уики
Преглед на файлове

删除没用的文件

wangwei преди 4 години
родител
32ccb300ee
ревизия
48618d7a43
променени са 11 файла, в които са добавени 0 реда и са изтрити 450 реда
Разделен изглед Покажи статистика за разликите
  1. 0 39
      .github/ISSUE_TEMPLATE/1-bug.md
  2. 0 32
      .github/ISSUE_TEMPLATE/2-feature.md
  3. 0 8
      .github/ISSUE_TEMPLATE/config.yml
  4. 0 89
      .github/commit-convention.md
  5. 0 5
      .github/contributing.md
  6. 0 34
      .github/pull_request_template.md
  7. 0 118
      .github/workflows/deploy.yml
  8. 0 55
      .github/workflows/ftp-schedule.yml
  9. 0 17
      .github/workflows/issue-close-require.yml
  10. 0 29
      .github/workflows/issue-labeled.yml
  11. 0 24
      .github/workflows/release.yml

+ 0 - 39
.github/ISSUE_TEMPLATE/1-bug.md
Целия файл 

@@ -1,39 +0,0 @@
 
----
 
-name: 🐛 Bug report
 
-about: Create a report to help us improve
 
-title: ''
 
-labels: 'bug: pending triage'
 
-assignees: ''
 
----
 
-
 
-<!--
 
-抱歉，您遇到了一个错误。感谢您抽出宝贵的时间进行举报！
 
-
 
-请尽可能填写以下模板。
 
-
 
-Ouch, sorry you’ve run into a bug.  Thank for taking the time to report it!
 
-
 
-Please fill in as much of the template below as you’re able.
 
-
 
-P.S. have you seen our support and contributing docs?
 
--->
 
-
 
-**⚠️ IMPORTANT ⚠️ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.**
 
-
 
-- [ ] Read [the docs](https://anncwb.github.io/vue-vben-admin-doc/).
 
-- [ ] Make sure the code is up to date. (Some bugs have been fixed in the latest code)
 
-- [ ] This is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/anncwb/vue-vben-admin/discussions) or join our [Discord](https://discord.gg/8GuAdwDhj6) Chat Server.
 
-
 
-### Describe the bug
 
-
 
-A clear and concise description of what the bug is..
 
-
 
-### Reproduction
 
-
 
-Please describe the steps of the problem in detail to ensure that we can restore the correct problem
 
-
 
-## System Info
 
-
 
-- Operating System:
 
-- Node version:
 
-- Package manager (npm/yarn/pnpm) and version:

+ 0 - 32
.github/ISSUE_TEMPLATE/2-feature.md
Целия файл 

@@ -1,32 +0,0 @@
 
----
 
-name: 🚀 Feature request
 
-about: Suggest an idea for this project
 
-title: ''
 
-labels: ''
 
-assignees: ''
 
----
 
-
 
-<!--
 
-感谢您提出使这个项目更好的想法！
 
-请尽可能填写以下模板。
 
-
 
-Thank you for suggesting an idea to make this project better!
 
-Please fill in as much of the template below as you’re able.
 
-
 
--->
 
-
 
-### Subject of the feature
 
-
 
-Describe your issue here.
 
-
 
-### Problem
 
-
 
-If the feature requests relates to a problem, please describe the problem you are trying to solve here.
 
-
 
-### Expected behaviour
 
-
 
-What should happen? Please describe the desired behaviour.
 
-
 
-### Alternatives
 
-
 
-What are the alternative solutions? Please describe what else you have considered?

+ 0 - 8
.github/ISSUE_TEMPLATE/config.yml
Целия файл 

@@ -1,8 +0,0 @@
 
-blank_issues_enabled: false
 
-contact_links:
 
-  - name: Discord Chat
 
-    url: https://discord.gg/8GuAdwDhj6
 
-    about: Ask questions and discuss with other Vben users in real time.
 
-  - name: Questions & Discussions
 
-    url: https://github.com/anncwb/vue-vben-admin/discussions
 
-    about: Use GitHub discussions for message-board style questions and discussions.

+ 0 - 89
.github/commit-convention.md
Целия файл 

@@ -1,89 +0,0 @@
 
-## Git Commit Message Convention
 
-
 
-> This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular).
 
-
 
-#### TL;DR:
 
-
 
-Messages must be matched by the following regex:
 
-
 
-```js
 
-/^(revert: )?(feat|fix|docs|style|refactor|perf|test|workflow|build|ci|chore|types|wip): .{1,50}/;
 
-```
 
-
 
-#### Examples
 
-
 
-Appears under "Features" header, `dev` subheader:
 
-
 
-```
 
-feat(dev): add 'comments' option
 
-```
 
-
 
-Appears under "Bug Fixes" header, `dev` subheader, with a link to issue #28:
 
-
 
-```
 
-fix(dev): fix dev error
 
-
 
-close #28
 
-```
 
-
 
-Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:
 
-
 
-```
 
-perf(build): remove 'foo' option
 
-
 
-BREAKING CHANGE: The 'foo' option has been removed.
 
-```
 
-
 
-The following commit and commit `667ecc1` do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header.
 
-
 
-```
 
-revert: feat(compiler): add 'comments' option
 
-
 
-This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
 
-```
 
-
 
-### Full Message Format
 
-
 
-A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
 
-
 
-```
 
-<type>(<scope>): <subject>
 
-<BLANK LINE>
 
-<body>
 
-<BLANK LINE>
 
-<footer>
 
-```
 
-
 
-The **header** is mandatory and the **scope** of the header is optional.
 
-
 
-### Revert
 
-
 
-If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body, it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
 
-
 
-### Type
 
-
 
-If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However, if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
 
-
 
-Other prefixes are up to your discretion. Suggested prefixes are `docs`, `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.
 
-
 
-### Scope
 
-
 
-The scope could be anything specifying the place of the commit change. For example `dev`, `build`, `workflow`, `cli` etc...
 
-
 
-### Subject
 
-
 
-The subject contains a succinct description of the change:
 
-
 
-- use the imperative, present tense: "change" not "changed" nor "changes"
 
-- don't capitalize the first letter
 
-- no dot (.) at the end
 
-
 
-### Body
 
-
 
-Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
 
-
 
-### Footer
 
-
 
-The footer should contain any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**.
 
-
 
-**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.

+ 0 - 5
.github/contributing.md
Целия файл 

@@ -1,5 +0,0 @@
 
-# Contributing Guide
 
-
 
-1. Make sure you put things in the right category!
 
-2. Always add your items to the end of a list. To be fair, the order is first-come-first-serve.
 
-3. If you think something belongs in the wrong category, or think there needs to be a new category, feel free to edit things too.

+ 0 - 34
.github/pull_request_template.md
Целия файл 

@@ -1,34 +0,0 @@
 
-### `General`
 
-
 
-> ✏️ Mark the necessary items without changing the structure of the PR template.
 
-
 
-- [ ] Pull request template structure not broken
 
-
 
-### `Type`
 
-
 
-> ℹ️ What types of changes does your code introduce?
 
-
 
-> 👉 _Put an `x` in the boxes that apply_
 
-
 
-- [ ] Bug fix (non-breaking change which fixes an issue)
 
-- [ ] New feature (non-breaking change which adds functionality)
 
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 
-- [ ] This change requires a documentation update
 
-
 
-### `Checklist`
 
-
 
-> ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in [CONTRIBUTING](contributing.md).
 
-
 
-> 👉 _Put an `x` in the boxes that apply._
 
-
 
-- [ ] My code follows the style guidelines of this project
 
-- [ ] Is the code format correct
 
-- [ ] Is the git submission information standard?
 
-- [ ] My code follows the style guidelines of this project
 
-- [ ] I have performed a self-review of my own code
 
-- [ ] I have commented my code, particularly in hard-to-understand areas
 
-- [ ] I have made corresponding changes to the documentation
 
-- [ ] My changes generate no new warnings
 
-- [ ] I have added tests that prove my fix is effective or that my feature works
 
-- [ ] New and existing unit tests pass locally with my changes
 
-- [ ] Any dependent changes have been merged and published in downstream modules

+ 0 - 118
.github/workflows/deploy.yml
Целия файл 

@@ -1,118 +0,0 @@
 
-name: deploy
 
-
 
-on:
 
-  push:
 
-    branches:
 
-      - main
 
-
 
-jobs:
 
-  # push-to-ftp:
 
-  #   if: "contains(github.event.head_commit.message, '[deploy]')"
 
-  #   runs-on: ubuntu-latest
 
-  #   steps:
 
-  #     - name: Checkout
 
-  #       uses: actions/checkout@v2
 
-
 
-  #     - name: Sed Config Base
 
-  #       shell: bash
 
-  #       run: |
 
-  #         sed -i  's#VITE_PUBLIC_PATH\s*=.*#VITE_PUBLIC_PATH = /next/#g' ./.env.production
 
-  #         sed -i  "s#VITE_BUILD_COMPRESS\s*=.*#VITE_BUILD_COMPRESS = 'gzip'#g" ./.env.production
 
-  #         cat ./.env.production
 
-
 
-  #     - name: use Node.js 14
 
-  #       uses: actions/setup-node@v2.1.2
 
-  #       with:
 
-  #         node-version: '14.x'
 
-
 
-  #     - name: Get yarn cache
 
-  #       id: yarn-cache
 
-  #       run: echo "::set-output name=dir::$(yarn cache dir)"
 
-
 
-  #     - name: Cache dependencies
 
-  #       uses: actions/cache@v2
 
-  #       with:
 
-  #         path: ${{ steps.yarn-cache.outputs.dir }}
 
-  #         key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
 
-  #         restore-keys: |
 
-  #           ${{ runner.os }}-yarn-
 
-
 
-  #     - name: Build
 
-  #       run: |
 
-  #         yarn install
 
-  #         yarn run build
 
-
 
-  #     - name: Deploy
 
-  #       uses: SamKirkland/FTP-Deploy-Action@2.0.0
 
-  #       env:
 
-  #         FTP_SERVER: ${{ secrets.FTP_SERVER }}
 
-  #         FTP_USERNAME: ${{ secrets.FTP_USERNAME }}
 
-  #         FTP_PASSWORD: ${{ secrets.FTP_PASSWORD }}
 
-  #         METHOD: sftp
 
-  #         PORT: ${{ secrets.FTP_PORT }}
 
-  #         LOCAL_DIR: dist
 
-  #         REMOTE_DIR: /srv/www/vben-admin
 
-  #         ARGS: --delete --verbose --parallel=80
 
-
 
-  push-to-gh-pages:
 
-    if: "contains(github.event.head_commit.message, '[release]')"
 
-    runs-on: ubuntu-latest
 
-    steps:
 
-      - name: Checkout
 
-        uses: actions/checkout@v2
 
-
 
-      - name: Sed Config Base
 
-        shell: bash
 
-        run: |
 
-          sed -i  's#VITE_PUBLIC_PATH\s*=.*#VITE_PUBLIC_PATH = /vben-admin-thin-next/#g' ./.env.production
 
-          sed -i  "s#VITE_BUILD_COMPRESS\s*=.*#VITE_BUILD_COMPRESS = 'gzip'#g" ./.env.production
 
-          cat ./.env.production
 
-
 
-      - name: use Node.js 14
 
-        uses: actions/setup-node@v2.1.2
 
-        with:
 
-          node-version: '14.x'
 
-
 
-      - name: Get yarn cache
 
-        id: yarn-cache
 
-        run: echo "::set-output name=dir::$(yarn cache dir)"
 
-
 
-      - name: Cache dependencies
 
-        uses: actions/cache@v2
 
-        with:
 
-          path: ${{ steps.yarn-cache.outputs.dir }}
 
-          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
 
-          restore-keys: |
 
-            ${{ runner.os }}-yarn-
 
-
 
-      - name: Set SSH Environment
 
-        env:
 
-          DOCS_DEPLOY_KEY: ${{ secrets.ACTIONS_DEPLOY_KEY }}
 
-        run: |
 
-          mkdir -p ~/.ssh/
 
-          echo "$ACTIONS_DEPLOY_KEY" > ~/.ssh/id_rsa
 
-          chmod 600 ~/.ssh/id_rsa
 
-          ssh-keyscan github.com > ~/.ssh/known_hosts
 
-          chmod 700 ~/.ssh && chmod 600 ~/.ssh/*
 
-          git config --local user.email "vbenadmin@163.com"
 
-          git config --local user.name "vbenAdmin"
 
-
 
-      - name: Delete gh-pages branch
 
-        run: |
 
-          git push origin --delete gh-pages
 
-
 
-      - name: Build
 
-        run: |
 
-          yarn install
 
-          yarn run build
 
-          touch dist/.nojekyll
 
-          cp dist/index.html dist/404.html
 
-
 
-      - name: Deploy
 
-        uses: peaceiris/actions-gh-pages@v2.5.0
 
-        env:
 
-          ACTIONS_DEPLOY_KEY: ${{secrets.ACTIONS_DEPLOY_KEY}}
 
-          PUBLISH_BRANCH: gh-pages
 
-          PUBLISH_DIR: ./dist
 
-        with:
 
-          forceOrphan: true

+ 0 - 55
.github/workflows/ftp-schedule.yml
Целия файл 

@@ -1,55 +0,0 @@
 
-name: schedule-push-to-ftp
 
-
 
-# Timed deployment project
 
-on:
 
-  push:
 
-  schedule:
 
-    - cron: '0 20 * * *'
 
-
 
-jobs:
 
-  schedule-push-to-ftp:
 
-    runs-on: ubuntu-latest
 
-    steps:
 
-      - name: Checkout
 
-        uses: actions/checkout@v2
 
-
 
-      - name: Sed Config Base
 
-        shell: bash
 
-        run: |
 
-          sed -i  's#VITE_PUBLIC_PATH\s*=.*#VITE_PUBLIC_PATH = /thin/next/#g' ./.env.production
 
-          sed -i  "s#VITE_BUILD_COMPRESS\s*=.*#VITE_BUILD_COMPRESS = 'gzip'#g" ./.env.production
 
-          cat ./.env.production
 
-
 
-      - name: use Node.js 14
 
-        uses: actions/setup-node@v2.1.2
 
-        with:
 
-          node-version: '14.x'
 
-
 
-      - name: Get yarn cache
 
-        id: yarn-cache
 
-        run: echo "::set-output name=dir::$(yarn cache dir)"
 
-
 
-      - name: Cache dependencies
 
-        uses: actions/cache@v2
 
-        with:
 
-          path: ${{ steps.yarn-cache.outputs.dir }}
 
-          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
 
-          restore-keys: |
 
-            ${{ runner.os }}-yarn-
 
-
 
-      - name: Build
 
-        run: |
 
-          yarn install
 
-          yarn run build
 
-
 
-      - name: Deploy
 
-        uses: SamKirkland/FTP-Deploy-Action@2.0.0
 
-        env:
 
-          FTP_SERVER: ${{ secrets.FTP_SERVER }}
 
-          FTP_USERNAME: ${{ secrets.FTP_USERNAME }}
 
-          FTP_PASSWORD: ${{ secrets.FTP_PASSWORD }}
 
-          METHOD: sftp
 
-          PORT: ${{ secrets.FTP_PORT }}
 
-          LOCAL_DIR: dist
 
-          REMOTE_DIR: /srv/www/vben-admin-thin
 
-          ARGS: --delete --verbose --parallel=80

+ 0 - 17
.github/workflows/issue-close-require.yml
Целия файл 

@@ -1,17 +0,0 @@
 
-name: Issue Close Require
 
-
 
-on:
 
-  schedule:
 
-    - cron: '0 0 * * *'
 
-
 
-jobs:
 
-  close-issues:
 
-    runs-on: ubuntu-latest
 
-    steps:
 
-      - name: need reproduction
 
-        uses: actions-cool/issues-helper@v2.1.1
 
-        with:
 
-          actions: 'close-issues'
 
-          token: ${{ secrets.OPER_TOKEN }}
 
-          labels: 'need reproduction'
 
-          inactive-day: 3

+ 0 - 29
.github/workflows/issue-labeled.yml
Целия файл 

@@ -1,29 +0,0 @@
 
-name: Issue Labeled
 
-
 
-on:
 
-  issues:
 
-    types: [labeled]
 
-
 
-jobs:
 
-  reply-labeled:
 
-    runs-on: ubuntu-latest
 
-    steps:
 
-      - name: remove pending
 
-        if: github.event.label.name == 'enhancement' || github.event.label.name == 'bug'
 
-        uses: actions-cool/issues-helper@v2.1.1
 
-        with:
 
-          actions: 'remove-labels'
 
-          token: ${{ secrets.OPER_TOKEN }}
 
-          issue-number: ${{ github.event.issue.number }}
 
-          labels: 'bug: pending triage'
 
-
 
-      - name: need reproduction
 
-        if: github.event.label.name == 'need reproduction'
 
-        uses: actions-cool/issues-helper@v2.1.1
 
-        with:
 
-          actions: 'create-comment, remove-labels'
 
-          token: ${{ secrets.OPER_TOKEN }}
 
-          issue-number: ${{ github.event.issue.number }}
 
-          body: |
 
-            Hello @${{ github.event.issue.user.login }}. Please provide the complete reproduction steps and code. Issues labeled by `need reproduction` will be closed if no activities in 3 days.
 
-          labels: 'bug: pending triage'

+ 0 - 24
.github/workflows/release.yml
Целия файл 

@@ -1,24 +0,0 @@
 
-name: Create Release
 
-
 
-on:
 
-  push:
 
-    tags:
 
-      - v*
 
-
 
-jobs:
 
-  build:
 
-    name: Create Release
 
-    runs-on: ubuntu-latest
 
-    steps:
 
-      - name: Checkout code
 
-        uses: actions/checkout@master
 
-
 
-      - name: Create Release for Tag
 
-        id: release_tag
 
-        uses: yyx990803/release-tag@master
 
-        env:
 
-          GITHUB_TOKEN: ${{ secrets.OPER_TOKEN }}
 
-        with:
 
-          tag_name: ${{ github.ref }}
 
-          body: |
 
-            Please refer to [CHANGELOG.md](https://github.com/anncwb/vue-vben-admin/blob/main/CHANGELOG.md) for details.