We would love for you to contribute to Runbox 7 and help make it even better than it is today!
Please see The Runbox 7 Roadmap and Runbox 7 Feature and Bug Bounty Program to help get you started.
As a contributor, here are the guidelines we would like you to follow:
Help us keep Runbox 7 open and inclusive. Please read and follow our Code of Conduct.
Please do not open issues on Github for general support questions as we want to keep GitHub issues for bug reports and feature requests.
- If you have a question or comment about Runbox 7: Please use our Runbox Forum at https://community.runbox.com. The Runbox Forum is the best place to ask questions as both Runbox Staff and other Runbox 7 users are there and happy to help. Also, questions and answers stay available for public viewing so they might help someone else.
- If you have an account specific issue: If your issue is account specific or involves personal details, we ask that you contact Runbox Support at https://support.runbox.com.
If you find a bug in the source code, you can help us by submitting an issue to our GitHub Repository. Even better, you can submit a Pull Request with a fix.
You can request a new feature by submitting an issue to our GitHub Repository.
If you would 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. Please consider what kind of change it is:
- For a Major Feature, first open an issue and outline your proposal so that it can be discussed. This will also allow us to better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project.
- Small Features can be crafted and directly submitted as a Pull Request.
Before you submit an issue, please search the issue tracker. Maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, please provide the following information:
- Operating system and browser version used.
- Whether or not a local index is used.
- Steps to reproduce the issue.
Before you submit your Pull Request (PR), consider the following guidelines:
- Search GitHub for an open or closed PR that relates to your submission. You don't want to duplicate effort.
- Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add. Discussing the design up front helps to ensure that we're ready to accept your work.
- Fork the runbox/runbox7 repo.
- Make your changes in a new git branch:
git checkout -b my-fix-branch master
- Create your patch, including appropriate test cases.
- Follow our Coding Rules.
- Run the full test suite (
npm run ci-tests), and ensure that all tests pass. - Commit your changes using a descriptive commit message that follows our commit message conventions. Adherence to these conventions is necessary because release notes are automatically generated from these messages.
git commit -a
Note: The optional commit -a command line option will automatically "add" and "rm" edited files.
- If you haven't done so already in step 7, generate and commit the updated changelog:
node src/build/build-changelog.js
git commit src/app/changelog/changes.ts -em "docs(changelog): Update changelog"
- Push your branch to GitHub:
git push origin my-fix-branch
- In GitHub, send a pull request to
runbox7:master.
- If we suggest changes then:
- Make the required updates.
- Re-run the test suites to ensure tests are still passing.
- Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
git rebase master -i git push -f
That's it! Thank you for your contribution!
After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository:
- Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
git push origin --delete my-fix-branch
- Check out the master branch:
git checkout master -f
- Delete the local branch:
git branch -D my-fix-branch
- Update your master with the latest upstream version:
git pull --ff upstream master
To ensure consistency throughout the source code, keep these rules in mind as you are working:
- All features or bug fixes must be tested by one or more specs (unit-tests).
- All public API methods must be documented.
- You may use
@author name/pseudonym(optionally email) inside comments for attribution.
We have very precise rules over how our Git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the Angular change log.
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
The header is mandatory and the scope of the header is optional.
Any line of the commit message cannot be longer than 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.
The footer should contain a closing reference to an issue if any.
Samples: (even more samples)
docs(changelog): Update changelog to beta.5
fix(release): Need to depend on latest rxjs and zone.js
The version in our package.json gets copied to the one we publish, and users need the latest of these.
If the commit is associated with an issue number, include it in the commit message body on the format #issuenumber (multiple allowed, separated by comma).
If the commit reverts a previous commit, it should begin with revert:, followed by the header of the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is the SHA of the commit being reverted.
Must be one of the following:
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
The subject contains a succinct description of the change:
- Use the imperative, present tense: "change" not "changed" nor "changes".
- No dot (.) at the end.
Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.
Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.
Contributions to this project indicate the contributors' assent for inclusion of that software in the canonical version under the project's license.