If you have questions about how to install or use Nextcloud, please direct these to our forum.
- Please search the existing issues and Discussions first, it's likely that your issue was already reported or even fixed.
- Go to https://github.com/nextcloud/all-in-one/discussions, and type any word in the top search/command bar.
- SECURITY: Report any potential security bug to us via our HackerOne page following our security policy instead of filing an issue in our bug tracker.
- The issues in other components should be reported in their respective repositories: You will find them in our GitHub Organization
- Report any issues then via https://github.com/nextcloud/all-in-one/discussions/new?category=questions.
Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues.
Thanks for wanting to contribute source code to Nextcloud. That's great!
Please read the general contribution guidelines that apply to all Nextcloud repositories, and the AI Contribution Policy if you are using AI tools. Please read the Developer Manuals to learn how to create your first application or how to test the Nextcloud code.
Nextcloud allows contributions made with the help of AI tools. You are the author of everything you submit - AI assistance does not change that responsibility.
-
Disclosure: Declare AI tool use in the PR description and add an
Assisted-by: AGENT_NAME:MODEL_VERSIONgit trailer to each affected commit. -
Accountability: You must be able to explain, defend, and modify every line you submit. If a reviewer asks why something works a certain way, "the AI wrote it" is not an answer.
-
Communication: PR descriptions and issue reports must be written in your own words.
-
Quality: AI output must be quality assured by the human, i.e. reviewed, cleaned up, and tested before submission.
-
Licensing: Ensure AI-generated code contains no material incompatible with the license of the repository you are contributing to.
For the full policy including autonomous agent rules, security reports, and beginner issues, read the AI Contribution Policy.
We are striving to increase the quality and reliability of our software by improving its test suite, and encourage to add or extend playwright test cases for every relevant code change.
We use the Developer Certificate of Origin (DCO) as a additional safeguard for the Nextcloud project. This is a well established and widely used mechanism to assure contributors have confirmed their right to license their contribution under the project's license. Please read contribute/developer-certificate-of-origin. If you can certify it, then just add a line to every git commit message:
Signed-off-by: Random J Developer <random@developer.example.org>
Use your real name (sorry, no pseudonyms or anonymous contributions).
If you set your user.name and user.email git configs, you can sign your
commit automatically with git commit -s. You can also use git aliases
like git config --global alias.ci 'commit -s'. Now you can commit with
git ci and the commit will be signed.
In case you are not sure how to add or update the license header correctly please have a look at contribute/HowToApplyALicense.md