-
Notifications
You must be signed in to change notification settings - Fork 283
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
ci: ensure sorted json files #1683
Conversation
@Leeyoungone No problem, just ping me when it's ready for review (I removed myself from the reviewers until then) |
@petermetz I've done the exact same thing for this PR that's linked to the issue I'm trying to solve and it seems like it's working while the other one isn't. I'm going to link this PR to the issue instead of the one that's currently linked to the issue I need to solve. Sorry for the confusion. |
8cd7f6e
to
b755db1
Compare
@petermetz Ready for review! |
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.
@Leeyoungone Sorry for the slow response! Please resolve the conflicts and then I'll have a go. Most likely the easiest to resolve the conflicts is to re-run the package.json sorting on whatever is on main right now instead of trying to resolve/untangle the conflicts manually.
f1fa6f5
to
cf8eaf9
Compare
@Leeyoungone Sorry, another conflict just popped up! :/ |
@petermetz all good, just fixed it :) |
2ffe621
to
6bf592e
Compare
a6bee5b
to
525a28a
Compare
@Leeyoungone No worries at all, thank you for updating it! |
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
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
305ef98
to
1caa560
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.
@Leeyoungone LGTM but you have a conflict again, sorry :-(
megasadge, it's okay I will fight the conflicts and win. brb |
I am done fighting the conflict :) |
@Leeyoungone Yay, nice, thank you and sorry for the slow response especially because in the meantime another conflict hit... :/ |
Sounds good! Thanks for letting me know :)) |
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.
@Leeyoungone Thank you, LGTM :-)
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.
@Leeyoungone Oops, sorry once again! I see that you have multiple commits but they do the same thing in the end. Could you please squash them into a single commit?
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.
@Leeyoungone LGTM
Fixes 1341 Signed-off-by: Youngone Lee <youngone.lee@accenture.com>
Fixes #1341
@petermetz