-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix: check git configuration before exec world create #74
base: daim/change_docker_compose_using_docker_api_sdk
Are you sure you want to change the base?
fix: check git configuration before exec world create #74
Conversation
Your org has enabled the Graphite merge queue for merging into mainAdd the label “graphite/merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## daim/change_docker_compose_using_docker_api_sdk #74 +/- ##
==================================================================================
Coverage ? 47.58%
==================================================================================
Files ? 52
Lines ? 2360
Branches ? 0
==================================================================================
Hits ? 1123
Misses ? 1039
Partials ? 198 ☔ View full report in Codecov by Sentry. |
d518417
to
e00d350
Compare
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.
The cleaner fix here is to do the git commit with an author flag like this such that the problem doesn't exist in the first place
git commit --author="World CLI [email protected]" -m "whatever"
oh man, this is a very good approach. I didn't think about that. 👍🏻 |
e00d350
to
b4a4011
Compare
@smsunarto i think the approach using i will bring back the checkGitConfig func. |
b4a4011
to
edf8145
Compare
Oh apparently it just lacks env. we can use :
|
edf8145
to
55608ae
Compare
ef6982b
to
0308c8f
Compare
55608ae
to
6052ac7
Compare
0308c8f
to
c5b6dbe
Compare
6052ac7
to
096d3c4
Compare
Merge activity
|
Closes: WORLD-1177 ## Overview When user trying to exec `world create` but git configuration `.gitconfig` for username and password is not configured it will be returned error, but the gameshard dir is already created. The issue is because on the last step of `world create` it will exec git commit, and it will need username and email to be configured in `.gitconfig` Solutions Before executing `world create`, world cli will check the git configuration is configured or not. if it's not, world cli will tell the command how to configure the git config. ## Brief Changelog - Create func for checking git configuration - Call the function at the first execution of `world create` command ## Testing and Verifying - Added unit test for checkGitConfig func
c5b6dbe
to
6eee015
Compare
096d3c4
to
4401cda
Compare
Closes: WORLD-1177
Overview
When user trying to exec
world create
but git configuration.gitconfig
for username and password is not configured it will be returned error, but the gameshard dir is already created.The issue is because on the last step of
world create
it will exec git commit, and it will need username and email to be configured in.gitconfig
Solutions
Before executing
world create
, world cli will check the git configuration is configured or not. if it's not, world cli will tell the command how to configure the git config.Brief Changelog
world create
commandTesting and Verifying