Skip to content

Conversation

KazuCocoa
Copy link
Member

Proposed changes

For #19851 (review)

Types of changes

What types of changes does your code introduce to Appium?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

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.

  • I have read the CONTRIBUTING doc
  • I have signed the CLA
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Base automatically changed from add-example-getsessions to master March 5, 2024 07:30
@KazuCocoa KazuCocoa marked this pull request as ready for review March 5, 2024 07:31
@github-actions github-actions bot added Bug a problem that needs fixing Documentation related to writing, reading, or generating documentation labels Mar 5, 2024
@KazuCocoa KazuCocoa merged commit 82b024c into master Mar 5, 2024
@KazuCocoa KazuCocoa deleted the docs-update-format branch March 5, 2024 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
appium core Bug a problem that needs fixing Documentation related to writing, reading, or generating documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants