Merge branch 'master' of github.com:gogf/gf into personal/hailaz

.github/FUNDING.yml

@@ -1,6 +1,6 @@
 # These are supported funding model platforms
 
-github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+github: [gogf] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
 patreon: # Replace with a single Patreon username
 open_collective: # Replace with a single Open Collective username
 ko_fi: # Replace with a single Ko-fi username
@@ -9,4 +9,4 @@ community_bridge: # Replace with a single Community Bridge project-name e.g., cl
 liberapay: # Replace with a single Liberapay username
 issuehunt: # Replace with a single IssueHunt username
 otechie: # Replace with a single Otechie username
-custom: https://github.com/gogf/gf#donators
+custom: # custom

.github/ISSUE_TEMPLATE/00-bug.yml

@@ -0,0 +1,71 @@
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+name: Bugs
+description: GoFrame command, module, or anything else
+title: "os/gtime: issue title"
+labels:
+  - bug
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping us improve! 🙏 Please answer these questions and provide as much information as possible about your problem.
+        
+        The issue title uses the format of the package name goes before the colon. Thanks!
+        
+        标题使用包名在冒号前的格式！谢谢！ 
+
+  - type: input
+    id: go-version
+    attributes:
+      label: Go version
+      description: |
+        What version of Go are you using (`go version`)?
+      placeholder: ex. go version go1.20.7 darwin/arm64
+    validations:
+      required: true
+
+  - type: input
+    id: gf-version
+    attributes:
+      label: GoFrame version
+      description: |
+        What version of GoFrame are you using (`gf version`)?
+      placeholder: ex. 2.7.0
+    validations:
+      required: true
+
+  - type: dropdown
+    id: is-reproducible
+    attributes:
+      label: Can this bug be reproduced with the latest release?
+      options:
+        - Option Yes
+        - Option No
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-did-you-do
+    attributes:
+      label: "What did you do?"
+      description: "If possible, provide a recipe for reproducing the error. A complete runnable program is good. A link on [go.dev/play](https://go.dev/play) is best."
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: "What did you see happen?"
+      description: Command invocations and their associated output, functions with their arguments and return results, full stacktraces for panics (upload a file if it is very long), etc. Prefer copying text output over using screenshots.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: "What did you expect to see?"
+      description: Why is the current output incorrect, and any additional context we may need to understand the issue.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/01-enhance.yml

@@ -0,0 +1,32 @@
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+name: Enhancements
+description: Enhance an idea for this project
+title: "os/gtime: issue title"
+labels:
+  - enhancement
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping us improve! 🙏 Please answer these questions and provide as much information as possible about your problem.
+        
+        The issue title uses the format of the package name goes before the colon. Thanks!
+        
+        标题使用包名在冒号前的格式！谢谢！ 
+
+  - type: textarea
+    id: description
+    attributes:
+      label: "Description"
+      description: "Please describe your idea in detail."
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: "Additional"
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/02-feature.yml

@@ -0,0 +1,48 @@
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+name: Features
+description: Suggest an idea for this project
+title: "os/gtime: issue title"
+labels:
+  - feature
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping us improve! 🙏 Please answer these questions and provide as much information as possible about your problem.
+        
+        The issue title uses the format of the package name goes before the colon. Thanks!
+        
+        标题使用包名在冒号前的格式！谢谢！ 
+
+  - type: dropdown
+    id: is-problem
+    attributes:
+      label: Is your feature request related to a problem?
+      options:
+        - Option Yes
+        - Option No
+    validations:
+      required: true
+
+  - type: textarea
+    id: description-solution
+    attributes:
+      label: "Describe the solution you'd like"
+    validations:
+      required: true
+
+  - type: textarea
+    id: description-considered
+    attributes:
+      label: "Describe alternatives you've considered"
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: "Additional"
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/03-question.yml

@@ -0,0 +1,25 @@
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+name: Questions
+description: I want to ask a question
+title: "os/gtime: issue title"
+labels:
+  - question
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please read the document carefully. 请先仔细阅读文档
+  
+        The issue title uses the format of the package name goes before the colon. Thanks!
+
+        标题使用包名在冒号前的格式！谢谢！ 
+
+  - type: textarea
+    id: ask
+    attributes:
+      label: "What do you want to ask?"
+      description: "Please describe the details of your questions. 请详细描述你的问题。"
+    validations:
+      required: true

.github/PULL_REQUEST_TEMPLATE.MD

@@ -0,0 +1,44 @@
+**Please ensure you adhere to every item in this list.**
++ The PR title is formatted as follows: `<type>[optional scope]: <description>` For example, `fix(os/gtime): fix time zone issue`
+  + `<type>` is mandatory and can be one of `fix`, `feat`, `build`, `ci`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`
+    + fix: Used when a bug has been fixed.
+    + feat: Used when a new feature has been added.
+    + build: Used for modifications to the project build system, such as changes to dependencies, external interfaces, or upgrading Node version.
+    + ci: Used for modifications to continuous integration processes, such as changes to Travis, Jenkins workflow configurations.
+    + docs: Used for modifications to documentation, such as changes to README files, API documentation, etc.
+    + style: Used for changes to code style, such as adjustments to indentation, spaces, blank lines, etc.
+    + refactor: Used for code refactoring, such as changes to code structure, variable names, function names, without altering functionality.
+    + perf: Used for performance optimization, such as improving code performance, reducing memory usage, etc.
+    + test: Used for modifications to test cases, such as adding, deleting, or modifying test cases for code.
+    + chore: Used for modifications to non-business-related code, such as changes to build processes or tool configurations.
+  + After `<type>`, specify the affected package name or scope in parentheses, for example, `(os/gtime)`.
+  + The part after the colon uses the verb tense + phrase that completes the blank in
+  + Lowercase verb after the colon
+  + No trailing period
+  + Keep the title as short as possible. ideally under 76 characters or shorter
+  + [Reference Documentation](https://www.conventionalcommits.org/en/v1.0.0/)
++ If there is a corresponding issue, add either `Fixes #1234` or `Updates #1234`
+  (the latter if this is not a complete fix) to this comment
++ Delete these instructions once you have read and applied them
+
+**提交前请遵守每个事项，感谢！**
++ PR 标题格式如下：`<类型>[可选 范围]: <描述>` 例如 `fix(os/gtime): fix time zone issue`
+  + `<类型>`是必须的，可以是 `fix`、`feat`、`build`、`ci`、`docs`、`style`、`refactor`、`perf`、`test`、`chore` 中的一个
+    + fix: 用于修复了一个 bug
+    + feat: 用于新增了一个功能
+    + build: 用于修改项目构建系统，例如修改依赖库、外部接口或者升级 Node 版本等
+    + ci: 用于修改持续集成流程，例如修改 Travis、Jenkins 等工作流配置
+    + docs: 用于修改文档，例如修改 README 文件、API 文档等
+    + style: 用于修改代码的样式，例如调整缩进、空格、空行等
+    + refactor: 用于重构代码，例如修改代码结构、变量名、函数名等但不修改功能逻辑
+    + perf: 用于优化性能，例如提升代码的性能、减少内存占用等
+    + test: 用于修改测试用例，例如添加、删除、修改代码的测试用例等
+    + chore: 用于对非业务性代码进行修改，例如修改构建流程或者工具配置等
+  + `<类型>`后在括号中填写受影响的包名或范围，例如 `(os/gtime)`
+  + 冒号后使用动词时态 + 短语
+  + 冒号后的动词小写
+  + 不要有结尾句号
+  + 标题尽量保持简短，最好在 76 个字符或更短
+  + [参考文档](https://www.conventionalcommits.org/zh-hans/v1.0.0/)
++ 如果有对应的 issue，请在此评论中添加 `Fixes #1234`，如果不是完全修复则添加 `Updates #1234`
++ 应用这些规则后删除所有的说明

.github/workflows/apollo/docker-compose.yml

@@ -20,7 +20,7 @@ services:
       #APOLLO_PORTAL_DB_PASSWORD: 'apollo'
 
   apollo-db:
-    image: "loads/mysql:5.7"
+    image: "mysql:5.7"
     container_name: apollo-db
     environment:
       TZ: Asia/Shanghai
@@ -36,7 +36,7 @@ services:
       - apollo-dbdata
 
   apollo-dbdata:
-    image: "loads/alpine:3.8"
+    image: "alpine:3.8"
     container_name: apollo-dbdata
     volumes:
       - /var/lib/mysql

.github/workflows/before_script.sh

@@ -1,6 +1,36 @@
 #!/usr/bin/env bash
 
-find . -name "*.go" | xargs gofmt -w
-git diff --name-only --exit-code || if [ $? != 0 ]; then echo "Notice: gofmt check failed,please gofmt before pr." && exit 1; fi
-echo "gofmt check pass."
+# Install gci
+echo "Installing gci..."
+go install github.com/daixiang0/gci@latest
+
+# Check if the GCI is installed successfully
+if ! command -v gci &> /dev/null
+then
+    echo "gci could not be installed. Please check your Go setup."
+    exit 1
+fi
+
+# Use GCI to format the code
+echo "Running gci to format code..."
+gci write \
+      --custom-order \
+      --skip-generated \
+      --skip-vendor \
+      -s standard \
+      -s blank \
+      -s default \
+      -s dot \
+      -s "prefix(github.com/gogf/gf/v2)" \
+      -s "prefix(github.com/gogf/gf/cmd)" \
+      -s "prefix(github.com/gogf/gf/contrib)" \
+      -s "prefix(github.com/gogf/gf/example)" \
+      ./
+
+# Check the code for changes
+git diff --name-only --exit-code || if [ $? != 0 ]; then echo "Notice: gci check failed, please gci before pr." && exit 1; fi
+echo "gci check pass."
+
+# Add the local domain name to `/etc/hosts`
+echo "Adding local domain to /etc/hosts..."
 sudo echo "127.0.0.1   local" | sudo tee -a /etc/hosts