【bug】A用户打开管理端页面长时间不刷新,中间时间B用户进行发布配置,B发布完成后A用户没刷新页面就直接通过文本模式修改配置,由于A用户不会重新加载当前最新配置,导致操作会覆盖当前最新配置,这个问题是否可以增加版本检查来避免此问题? #7798
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# | |
# Copyright 2024 Apollo Authors | |
# | |
# Licensed under the Apache License, Version 2.0 (the "License"); | |
# you may not use this file except in compliance with the License. | |
# You may obtain a copy of the License at | |
# | |
# http://www.apache.org/licenses/LICENSE-2.0 | |
# | |
# Unless required by applicable law or agreed to in writing, software | |
# distributed under the License is distributed on an "AS IS" BASIS, | |
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
# See the License for the specific language governing permissions and | |
# limitations under the License. | |
# | |
name: "CLA Assistant" | |
on: | |
issue_comment: | |
types: [created] | |
pull_request_target: | |
types: [opened,closed,synchronize] | |
jobs: | |
CLAssistant: | |
runs-on: ubuntu-latest | |
steps: | |
- name: "CLA Assistant" | |
if: (github.event.comment.body == 'recheck' || startsWith(github.event.comment.body, 'I have read the CLA Document and I hereby sign the CLA')) || github.event_name == 'pull_request_target' | |
# Beta Release | |
uses: cla-assistant/[email protected] | |
env: | |
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
# the below token should have repo scope and must be manually added by you in the repository's secret | |
PERSONAL_ACCESS_TOKEN : ${{ secrets.PERSONAL_ACCESS_TOKEN_FOR_CLA_ASSISTANT }} | |
with: | |
path-to-signatures: 'signatures/version1/cla.json' | |
path-to-document: 'https://github.com/apolloconfig/apollo-community/blob/master/CLA.md' # e.g. a CLA or a DCO document | |
# branch should not be protected | |
branch: 'master' | |
allowlist: dependabot,bot*,github-actions | |
remote-repository-name: apollo-community | |
#below are the optional inputs - If the optional inputs are not given, then default values will be taken | |
#remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository) | |
#remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository) | |
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures' | |
#signed-commit-message: 'For example: $contributorName has signed the CLA in #$pullRequestNo' | |
#custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign' | |
#custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA' | |
#custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.' | |
#lock-pullrequest-aftermerge: false - if you don't want this bot to automatically lock the pull request after merging (default - true) | |
#use-dco-flag: true - If you are using DCO instead of CLA |