-
Notifications
You must be signed in to change notification settings - Fork 672
Frequently Asked Questions (Developers)
Oskar W edited this page Apr 2, 2022
·
4 revisions
- Please leave a comment with your PR at the referring Jira ticket and ask for a review.
- Sometimes it can take a few days for one of our members with writing access to see the comment, please be patient and do not ping any members in the comments.
- If any tests fail please:
- make sure that you really did not change any code which could be related to the issue
- make sure that they pass locally(always)
- write the failing tests into the PR so the reviewer can take a closer look into it
- If you want to to contribute to our projects, we suggest starting by forkingthe repository of the project you want to contribute to. Then you can take a look at our issue-tracker and start by looking at the tickets. The first training ticket usually consists of writing a new Catrobat language test. To do so, please take a look at https://jira.catrob.at/browse/CATROID-390 and How to do Catrobat language tests. We strictly use test driven development and clean code, so read everything you can about these development methods before starting any ticket. Afterwards you can follow Branch and Commit Message Guidelines and Creating a pull request to get your ticket merged.
-
There are gradle tasks to run every static code analyzing tool
Tool Gradle task Checkstyle checkstyle
PMD pmd
Lint lint
All tools above at once check
You can run all gradle tasks either in the
- Terminal
- e.g.
./gradlew checkstyle
- Android Studio
-
The result can be found in the Gradle Console.