Skip to content

Commit e55a80b

Browse files
committed
docs: add contributing guide.
1 parent e1c4d3c commit e55a80b

File tree

1 file changed

+56
-0
lines changed

1 file changed

+56
-0
lines changed

CONTRIBUTING.md

+56
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
# Contributing to AppleSimulatorUtils (ASU)
2+
So, you want to contribute to ASU? Great! 👏
3+
Here are a few guidelines that will help you along the way. There are many ways to contribute, and we appreciate all of them.
4+
5+
## Before you start
6+
7+
ASU is a collection of utils for Apple simulators.
8+
It is a command line tool that allows you to set permissions for apps running on simulators, clear the simulator's keychain and media, and more.
9+
10+
We created this tool on Wix to help us with our development and testing, and it is mainly used by our testing framework, [Detox](https://wix.github.io/Detox/) (which is also an open source project), but can be used independently.
11+
12+
### Asking questions
13+
If you have a question, please open an issue in the Issues section of the project. Feel free to ask anything, even if you're not sure it's a bug or an enhancement. We'll do our best to answer, or redirect you to the right place.
14+
The more information you provide, the better we can help you.
15+
16+
### Reporting bugs
17+
If you find a bug, please report it in the [issues](http://github.com/wix/AppleSimulatorUtils/issues) section of the project.
18+
19+
### Suggesting enhancements
20+
For feature requests or suggestions, please open an issue in the Issues section of the project. Please provide as much information as possible, to help us understand what you're looking for.
21+
If you'd like to implement a new feature, please submit an issue with a proposal for your work first, to be sure that we can use it. When you are ready to start, please follow the instructions in the [Contributing code](#contributing-code) section below.
22+
23+
### Help others
24+
Help others by answering questions in the Issues section. If you see a question that you know the answer to, please help out! It's a great way to learn, and to help others.
25+
26+
### We ❤️ Pull Requests!
27+
**We are happy to accept contributions to ASU from the community!**
28+
Please read the following [guidelines](#contributing-code) before you start working on a pull request.
29+
30+
31+
## Contributing code
32+
33+
ASU is a homebrew package, therefore it can be installed using the `brew` command:
34+
```shell
35+
brew tap wix/brew
36+
brew install applesimutils
37+
```
38+
39+
However, if you are interested in changing ASU code and to contribute to it, the following steps are required.
40+
1. Clone the repository to your local machine.
41+
2. Make sure you have Xcode installed.
42+
3. Open the `applesimutils.xcodeproj` file in Xcode.
43+
4. Make your changes.
44+
5. Build the project from the Xcode: `Product > Build` or `⌘B`.
45+
6. Set the scheme launch arguments to the desired command line arguments you want to test (e.g. `--list`). This can be done by clicking on the scheme name in the top left corner of Xcode, and then selecting `Edit Scheme...`. In the `Arguments` tab, select or add the desired arguments to the `Arguments Passed On Launch` section.
46+
7. Run and play with the tool from the Xcode: `Product > Run` or `⌘R`.
47+
1. Set breakpoints to debug your changes.
48+
2. Plan a manual test scenario and run it (unfortunately, we don't have automated tests for this project). Make sure the output is as expected.
49+
8. Commit your changes and open a pull request.
50+
1. Add a description of your changes.
51+
2. Describe how to test them (how you tested them).
52+
3. Add a link to the issue you are fixing, if there is one.
53+
9. Wait for the pull request to be reviewed our team and merged.
54+
10. If everything went well, your changes will be available in the next release of ASU.
55+
56+
Thank you for your contribution! 🎉

0 commit comments

Comments
 (0)