-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Trunk-5480 Make ModuleUtil support more version specification format #2832
Conversation
@mks-d Can you review it please? I know that the documentation changes are not very good but i dont know how to get it right. Thanks a lot. |
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.
Could you for each test case test thoroughly as many as possible edge cases based on the requiredOpenmrsVersion
? I provided an example.
@mks-d added the tests for edge cases . I hope that i didnt miss something . I wait your review . Thanks |
@mks-d i think i broke the commit history by trying to squash this branch. How can i fix? |
Locally, start off a fresh master and cherry-pick the one commit on top: git checkout -b tmp upstream/master
git cherry-pick 0d83e403ccd1a1a332404b97c9701abc3b724c75
# here make sure that you have indeed the latest master PLUS the one commit
git log -20 --oneline --format='%h %<(150,trunc)%s'
# now let's archive the current TRUNK-5480
git branch -m TRUNK-5480 archive
# now let's make tmp the new TRUNK-5480
git branch -m TRUNK-5480
# finally let's push off the new TRUNK-5480
git push -f origin TRUNK-5480 I'm assuming that your remote is named |
@mks-d it worked like a charm .Thank you very much . |
Added the edge cases tests
@mks-d thanks for review . I did the requested changes. |
@mks-d i think the PR is almost ready for merge. |
@mks-d this pr needs 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.
I find the Changes made good
e8f7850
to
1877e06
Compare
Description of what I changed
Issue I worked on
see https://issues.openmrs.org/browse/TRUNK-5480
Checklist: I completed these to help reviewers :)
My pull request only contains ONE single commit
(the number above, next to the 'Commits' tab is 1).
No? -> read here on how to squash multiple commits into one
My IDE is configured to follow the code style of this project.
No? Unsure? -> configure your IDE, format the code and add the changes with
git add . && git commit --amend
I have added tests to cover my changes. (If you refactored
existing code that was well tested you do not have to add tests)
No? -> write tests and add them to this commit
git add . && git commit --amend
I ran
mvn clean package
right before creating this pull request andadded all formatting changes to my commit.
No? -> execute above command
All new and existing tests passed.
No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.
My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command
git pull --rebase upstream master