Skip to content

Latest commit

 

History

History
75 lines (50 loc) · 3.92 KB

CONTRIBUTING.md

File metadata and controls

75 lines (50 loc) · 3.92 KB

Submitting issues

If you have questions about how to use ownCloud, please direct these to the mailing list or our forum. We are also available on IRC.

Guidelines

If your issue appears to be a bug, and hasn't been reported, open a new issue.

Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues.

Contributing to Source Code

Thanks for wanting to contribute source code to ownCloud. That's great!

Before we're able to merge your code into the ownCloud app for Android, you need to sign our Contributor Agreement.

Guidelines

  • Contribute your code in the branch 'master'. It will give us a better chance to test your code before merging it with stable code.
  • For your first contribution, start a pull request on master and send us the signed Contributor Agreement.
  • Keep on using pull requests for your next contributions although you own write permissions.

1. Fork and download android/master repository:

NOTE: You must have the git installation folder in your environment variable PATH to perform the next operations.

  • In a web browser, go to https://github.com/owncloud/android, and click the 'Fork' button near the top right corner.
  • In a command line prompt, clone your new repo: git clone [email protected]:YOURGITHUBNAME/android.git.
  • Move to the project folder with cd android.
  • Checkout the remote branch 'master' in your own local branch: git checkout -b master remotes/origin/master.
  • Pull any changes from your remote branch 'master': git pull origin master
  • Make official ownCloud repo known as upstream: git remote add upstream [email protected]:owncloud/android.git
  • Make sure to get the latest changes from official android/master branch: git pull upstream master
  • Make sure you read SETUP.md when you start working on this project.

7. Create pull request:

NOTE: You must sign the Contributor Agreement before your changes can be accepted!

8. Create another pull request:

To make sure your new pull request does not contain commits which are already contained in previous PRs, create a new branch which is a clone of upstream/master.

  • git fetch upstream
  • git checkout -b my_new_master_branch upstream/master
  • If you want to rename that branch later: git checkout -b my_new_master_branch_with_new_name
  • Push branch to server: git push -u origin name_of_local_master_branch
  • Use GitHub to issue PR

Translations

Please submit translations via Transifex.