-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optimize:update the Group name in deploy.md #924
Conversation
@slievrly Updated the deployment documents of the official website |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current needs to change
hello,I don't quite understand what that means, is there anything else I need to do |
In the PR, you updated the documents for versions 2.1 and 2.2. Besides that, it also involves the current version (which will be the next release). Here’s the link to it. You’ll need to make sure to submit the changes to these two directories as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I will submit a new PR for the changes that PR needs to submit.
What is the purpose of the change
Since the io.seata package name has been changed to org.apache.seata since version 2.1, but the corresponding deployment document has not changed, this submission will keep the deployment document consistent with the GAV coordinates of seata
由于从2.1版本开始,seata-server已经将io.seata包名改为了org.apache.seata,但是对应的部署文档仍然没有变更,此次提交将把部署文档和seata 的GAV坐标保持一致
Brief changelog
i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.1/ops/deploy-guide-beginner.md
i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.2/ops/deploy-guide-beginner.md
Follow this checklist to help us incorporate your contribution quickly and easily:
doc: add an operations guide document
. Each commit within the pull request should contain a meaningful subject line and body.npm run build
, and make sure it works as expected.build
folder are included in the commit, as well as thepackage-lock.json
andyarn.lock
files.