mobile-dev-inc / mobile-dev-inc/maestro-docs
Update docs for newly added commands
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 85
- Forks
- 92
- Avg merge
- 16h 6m
- Merged PRs (30d)
- 1
Description
We've recently merged many PRs. The ones that need documentation update: (in order from newest to oldest):
- https://github.com/mobile-dev-inc/maestro/pull/1946 -> #91
- https://github.com/mobile-dev-inc/maestro/pull/1829
- https://github.com/mobile-dev-inc/maestro/pull/1955 -> #90
- https://github.com/mobile-dev-inc/maestro/pull/1954
- https://github.com/mobile-dev-inc/maestro/pull/1945
- https://github.com/mobile-dev-inc/maestro/pull/1999
- https://github.com/mobile-dev-inc/maestro/pull/2002
- https://github.com/mobile-dev-inc/maestro/pull/1987
- https://github.com/mobile-dev-inc/maestro/pull/1947
- https://github.com/mobile-dev-inc/maestro/pull/1988
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the four unchecked pull requests linked in this issue: #1829, #1945, #2002, and #1987. Compare the commands they added with the existing maestro-docs content, update the relevant documentation, and consider the work done when each unchecked item is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100