Fetching contributors…
Cannot retrieve contributors at this time
321 lines (252 sloc) 12.4 KB

Contributing to NativeScript

👍 First of all, thank you for taking the time to contribute! 👍

Here are some guides on how to do that:

Code of Conduct

Help us keep a healthy and open community. We expect all participants in this project to adhere to the NativeScript Code Of Conduct.

Reporting Bugs

  1. Always update to the most recent master release; the bug may already be resolved.
  2. Search for similar issues in the issues list for this repo; it may already be an identified problem.
  3. If this is a bug or problem that is clear, simple, and is unlikely to require any discussion -- it is OK to open an issue on GitHub with a reproduction of the bug including workflows and screenshots. If possible, submit a Pull Request with a failing test, entire application or module. If you'd rather take matters into your own hands, fix the bug yourself (jump down to the Submitting a PR section).

While we are doing all we can to take care of every issue, sometimes we get overwhelmed. That's why

  • issues that are not constructive or describe problems that cannot be reproduced will be closed
  • feature requests or bug reports with unanswered questions regarding the behavior/reproduction for more than 20 days will be closed

Requesting Features

  1. Use Github Issues to submit feature requests.
  2. First, search for a similar request and extend it if applicable. This way it would be easier for the community to track the features.
  3. When requesting a new feature, please provide as much detail as possible about why you need the feature in your apps. We prefer that you explain a need rather than explain a technical solution for it. That might trigger a nice conversation on finding the best and broadest technical solution to a specific need.

Submitting a PR

Before you begin:

Following these steps is the best way to get you code included in the project:

  1. Fork and clone the NativeScript repo:
git clone<your-git-username>/NativeScript.git
# Navigate to the newly cloned directory
cd NativeScript
# Add an "upstream" remote pointing to the original {N} repo.
git remote add upstream
  1. Set up the project (for detailed info check our development workflow guide):
#In the repo root
npm install
npm run setup
  1. Create a branch for your PR
git checkout -b <my-fix-branch> master
  1. The fun part! Make your code changes. Make sure you:

  2. Before you submit your PR:

    • Rebase your changes to the latest master: git pull --rebase upstream master.
    • Ensure all unit test are green for Android and iOS. Check running unit tests.
    • Ensure your changes pass tslint validation. (run npm run tslint in the root of the repo).
  3. Push your fork. If you have rebased you might have to use force-push your branch:

git push origin <my-fix-branch> --force
  1. Submit your pull request. Please, fill in the Pull Request template - it will help us better understand the PR and increase the chances of it getting merged quickly.

It's our turn from there on! We will review the PR and discuss changes you might have to make before merging it! Thanks!

Note: Sometimes you will see someone from the contributors team writing strange comments like: test or test branch_functional_tests#css-gradients-tests branch_widgets#vultix/css-gradients - don't worry about it, these are just phrases that trigger the internal CI builds.

Commit Message Guidelines

Please follow the git commit message format described below when committing your changes or submitting a PR. That allows us to use the commit messages to generate a change log for every new release.

Commit Message Format

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>

The header is mandatory and the scope of the header is optional.

Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.

Footer should contain a closing reference to an issue if any.


docs(README): add link to NativeScript roadmap
fix(ios-layouts): switch contentInsetAdjustmentBehavior on ScrollView

Do not auto adjust the ScrollView insets, by disabling contentInsetAdjustmentBehavior property, when ScrollView is used as a root Page element.
release: cut the 3.2.0 release


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: npm, grunt)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Jenkins)
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bug fix
  • fix-next: A fix for a bug in the master branch, that's not yet released
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature
  • release: Reference commit for the git tag of the release
  • 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 (example scopes: e2e, name-of-the-test-app)


The scope should be the name of the affected component in the code. If the change affects only one of the target platforms (android, ios) that should be specified in the scope.

Sample scopes for the tns-core-modules package:

  • android/application
  • ios/application
  • action-bar
  • animations
  • date-picker
  • profiling


The subject contains succinct description of the change:

  • use the imperative, present tense: "change" not "changed" nor "changes"
  • don't capitalize first letter
  • 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. Describe the changes and provide a migration guide for any code that may be affected. Sample:

feat: Angular 4.2 support


NativeScriptModule should be imported only in the root application
module (usually named AppModule).
All other NgModules in the app (both feature and lazy-loaded ones)
should import the NativeScriptCommonModule instead.
The behavior is aligned with BrowserModule and CommonModule in web
Angular apps.
Migration steps:
In all NgModules, instead of the root one, replace:

import { NativeScriptModule } from "nativescript-angular/nativescript.module";
    imports: [


import { NativeScriptCommonModule } from "nativescript-angular/common";
    imports: [

The above guidelines are based on the AngularJS Git Commit Message Conventions. A detailed explanation and additional examples can be found in this document.

Where to Start

If you want to contribute, but you are not sure where to start - look for issues labeled help wanted.

Releasing new versions

Instructions how to release a new version for NativeScript Core Team Members.

Here are the steps described in the diagram above.

  1. Checkout release branch
git checkout release
  1. Create a PR to cut the release:
export RELEASE_VERSION=version
export BRANCH="release-${RELEASE_VERSION}"
git checkout -b ${BRANCH}
git push --set-upstream origin ${BRANCH}

Merge master in release branch or cherry-pick commits. If the commits are in release branch skip this step.

git merge --ff-only origin/master or git cherry-pick commit-sha
git push --set-upstream origin prep-release-version
  1. Execute npm i to install dependencies:
npm i
  1. Execute npm version to bump the version of tns-platform-declarations:
cd tns-platform-declarations
npm --no-git-tag-version version [major|minor|patch] -m "release: cut the %s release"
cd ..
  1. Execute npm version to bump the version of tns-core-modules, tag the release and update the In case we need to publish release version we need simply to use npm version x.x.x-rc
cd tns-core-modules
npm --no-git-tag-version version [major|minor|patch] -m "release: cut the %s release"
cd ..
  1. Set correct version of tns-core-modules-widgets in tns-core-modules/package.json. Usually tns-core-modules-widgets should already have been released and we need to set the official version.

  2. Add changes

git add changed-files
git commit -m "release: cut the %s release"
git push
  1. Create git tag
git tag release-version
git push --tags
  1. Create a pull request. Replace env variables ${RELEASE_VERSION} and ${BRANCH} with their values
curl -d '{"title": "release: cut the ${RELEASE_VERSION} release","body": "docs: update changelog","head": "${BRANCH}","base": "release"}' -X POST -H "Authorization: token ${GIT_TOKEN}"
  1. Merge PR into release branch.

  2. If all checks has passed publish package.

Merge changes from release into master

Here are steps described in the diagram above.

  1. Make sure you are in release branch:
git checkout release
git pull
  1. Create PR to merge changes back in master and preserve history:
export MERGE_BRANCH='merge-release-in-master'
git checkout -b ${MERGE_BRANCH}
git push --set-upstream origin ${MERGE_BRANCH}
git merge origin/master
  1. Resolve conflicts. Choose to keep the version of master branch. If it is needed to revert versions of modules, see at the bottom.

  2. Add conflicts:

git add resolved files
  1. Commit changes with default merge message:
git commit
git push
  1. Create pull request. Replace replace env ${MERGE_BRANCH} with its value
curl -d '{"title": "chore: merge release in master","body": "chore: merge release in master","head": "merge-release-in-master","base": "master"}' -X POST -H "Authorization: token ${GIT_TOKEN}"

If needed, revert version of modules and platform declarations to take the one from master:

git checkout origin/master tns-platform-declarations/package.json tns-core-modules/package.json
git commit --amend
git push --force-with-lease

This will require to repeat steps from 1 to 4, since we need to keep the branches with the same history