Google Utility Sync Data
Utility functions to access some GCP Resources made ES6.
How to install
- To install all dependencies you can use the following commands:npm install
How to run unit tests.
- To run all unit tests you can use the following commands:npm test
See the .nycrc file to see our target QA numbers.
To run coverage execution use the following commands:
npm run cov
A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0. Reference link.
It’s common practice to prefix your version names with the letter v. Some good tag names might be v1.0 or v2.3.4.
If the tag isn’t meant for production use, add a pre-release version after the version name. Some good pre-release versions might be v0.2-alpha or v5.9-beta.3.
If you’re new to releasing software, we highly recommend reading about semantic versioning.
Releases / Creating Releases
Note: Only users with write access to the repository can view drafts of releases. For more information, see:
- On GitHub, navigate to the main page of the repository.
- Under your repository name, click Releases.
- Click Draft a new release.
- Type a version number for your release. Versions are based on Git tags. We recommend naming tags that fit within semantic versioning.
- Select a branch that contains the project you want to release. Usually, you'll want to release against your master branch, unless you're releasing beta software.
- Type a title and description that describes your release.
- If you'd like to include binary files along with your release, such as compiled programs, drag and drop or select files manually in the binaries box.
- If the release is unstable, select This is a pre-release to notify users that it's not ready for production.
- If you're ready to publicize your release, click Publish release. Otherwise, click Save draft to work on it later.