@DeviaVir
There are two ways to push from the travis to the repository.

Use token of github
Use deploy key

In the case of token, it affects the whole user who created token, but in the case of deploy key, it affects only the registered repository.
Since the impact range is small, we adopted a method using deploy key.

I made a sample up to pushing to master with travis.

Use travis-scripts
- Install and setup according to the document.
- % npm install @alrra/travis-scripts --save-dev
- doc: https://github.com/alrra/travis-scripts
Updating travis.yml & release-script.sh
- sample: https://github.com/abetomo/node-ss2json/blob/master/.travis.yml
```
- stage: Preparation of npm
node_js: "7"
script: "./release-script.sh"
```
Compared to the file in node-lambda now, the above three lines have been added.
- sample: https://github.com/abetomo/node-ss2json/blob/master/release-script.sh
How to release
- Pushing a branch whose branch name begins with release/ will be executed until release.

===
If you write everything here, it will be long, so I will only describe the summary and it will end.
Although it is a brief explanation in release-script.sh(https://github.com/abetomo/node-ss2json/blob/master/release-script.sh), I left a comment.
However, I omitted a detailed explanation.
If you have any questions, please ask a question.

Version increment/deploy path #276

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions