Closed MasihTak closed 3 years ago
Hi @chgasparoto sorry for that, I fixed the issue.
Merging #46 (19f2ba6) into master (cd15e28) will increase coverage by
100.00%
. The diff coverage is100.00%
.
@@ Coverage Diff @@
## master #46 +/- ##
=============================================
+ Coverage 0 100.00% +100.00%
=============================================
Files 0 1 +1
Lines 0 39 +39
Branches 0 3 +3
=============================================
+ Hits 0 39 +39
Impacted Files | Coverage Δ | |
---|---|---|
src/index.js | 100.00% <100.00%> (ø) |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update cd15e28...50225f9. Read the comment docs.
@masihtak please update the README.md file with your implementation.
Code looks good, you just need to fix the conflict with README.md file, please.
What changes needed for the README.md file ? I already added implementation
@masihtak you are right, there's no implementation to do but there are conflicts to be resolved before the merge. See below 👇
It's because branch, isn't?
yes, I've merged other branches into master, so it's normal to get some conflicts.
So what should I do? should I make new request?
I'll wait one more week for the conflict fix otherwise I'm going to close it 😉
:tada: This PR is included in version 1.20.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Proposed changes
Added Spanish helper method fix #32
Types of changes
What types of changes does your code introduce to Appium? Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.