Feat fix go import #536
Merged
Feat fix go import #536
Conversation
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
init github actions
add apache license
* bugfix: repair init getty failed
* remove unused config
* bugfix: at model execution failed
* temporary not supported connection-num
* fix bug
add change log for v1.0.2-RC3
Co-authored-by: liuyuecai <liuyuecai@didiglobal.com>
georgehao
approved these changes
Apr 7, 2023
AlexStocks
approved these changes
Apr 7, 2023
luky116
approved these changes
Apr 8, 2023
georgehao
pushed a commit
to georgehao/seata-go
that referenced
this pull request
Apr 8, 2023
optimize go imports style
georgehao
pushed a commit
to georgehao/seata-go
that referenced
this pull request
May 7, 2023
optimize go imports style
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
Which issue(s) this PR fixes:
fix goimport script invalid
Fixes #493
Special notes for your reviewer:
Does this PR introduce a user-facing change?: