Skip to content
This repository was archived by the owner on Jan 8, 2025. It is now read-only.

Commit 265c8ae

Browse files
committed
Merge branch 'release/1.2.6'
2 parents 2f934e0 + 8c654ad commit 265c8ae

File tree

5 files changed

+2363
-1697
lines changed

5 files changed

+2363
-1697
lines changed

.eslintrc.js

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
module.exports = {
22
extends: ['standard', 'plugin:prettier/recommended'],
3-
plugins: ['import', 'mocha'],
3+
plugins: ['mocha'],
44
parserOptions: {
55
sourceType: 'module'
66
},

CONTRIBUTING.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ See this handy, if ugly, [cheat sheet](http://danielkummer.github.io/git-flow-ch
1616
2. clone your fork to your local development machine
1717
3. Set this repo as the `upstream` repo `git remote add upstream <insert the upstream url>`
1818
4. Disallow direct pushing to upstream `git remote set-url --push upstream no_push`
19-
5. create a local `master` branch `git checkout -b master` and test it via `git pull upstream master`
19+
5. create a local `main` branch `git checkout -b main` and test it via `git pull upstream main`
2020
6. ensure you have installed the [`git-flow` command line helpers](https://github.com/nvie/gitflow) and [`git-flow-completion` utils](https://github.com/bobthecow/git-flow-completion) then run `git flow init -d`.
2121

2222
#### Optional Git Setup
@@ -46,15 +46,15 @@ git config user.email "[email protected]"
4646

4747
#### Hotfixes and Support branches
4848

49-
It's basically the same process but use the word `hotfix` or `support` instead of `feature`. `git flow` knows what to do. Just keep in mind that any changes are going to happen to your fork, and not the upstream repo. If you need to merge a `hotfix` into upstream master you may only do it va a reviewed pull request.
49+
It's basically the same process but use the word `hotfix` or `support` instead of `feature`. `git flow` knows what to do. Just keep in mind that any changes are going to happen to your fork, and not the upstream repo. If you need to merge a `hotfix` into upstream main you may only do it va a reviewed pull request.
5050

5151
### Releasing to production
5252

5353
1. `git flow release start {tag.number}` (using semantic versioning)
5454
2. commit any changes to version info in `package.json` then `git flow release publish {tag.number}`
55-
3. `git flow release finish {tag.number}` merges the release into `master` of your fork, tags it, merges that back into `develop` on your fork and removes the release branch.
56-
4. Now go back to GitHub and raise a Pull Request to merge the upstream master from your fork's `master` branch. When that goes through you are done.
57-
5. In your command-line go back and clean up any outstanding branches and `git pull upstream` your local `master` and `develop` branches to ensure everything on your local machine is up to date with everyone's changes.
55+
3. `git flow release finish {tag.number}` merges the release into `main` of your fork, tags it, merges that back into `develop` on your fork and removes the release branch.
56+
4. Now go back to GitHub and raise a Pull Request to merge the upstream main from your fork's `main` branch. When that goes through you are done.
57+
5. In your command-line go back and clean up any outstanding branches and `git pull upstream` your local `main` and `develop` branches to ensure everything on your local machine is up to date with everyone's changes.
5858

5959
Note you will **never** push changes directly to the upstream project, _only to your own fork_.
6060

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ I've paired this right back to the simplest, most generic API I could, so there'
9191
| Branch | Tests | Code Coverage | Audit | Comments |
9292
| ------ | ----- | ------------- | ----- | -------- |
9393
| `develop` | [![CircleCI](https://circleci.com/gh/davesag/api-server-boilerplate/tree/develop.svg?style=svg)](https://circleci.com/gh/davesag/api-server-boilerplate/tree/develop) | [![codecov](https://codecov.io/gh/davesag/api-server-boilerplate/branch/develop/graph/badge.svg)](https://codecov.io/gh/davesag/api-server-boilerplate) | [![Vulnerabilities](https://snyk.io/test/github/davesag/api-server-boilerplate/develop/badge.svg)](https://snyk.io/test/github/davesag/api-server-boilerplate/develop) | Work in progress |
94-
| `master` | [![CircleCI](https://circleci.com/gh/davesag/api-server-boilerplate/tree/master.svg?style=svg)](https://circleci.com/gh/davesag/api-server-boilerplate/tree/master) | [![codecov](https://codecov.io/gh/davesag/api-server-boilerplate/branch/master/graph/badge.svg)](https://codecov.io/gh/davesag/api-server-boilerplate) | [![Vulnerabilities](https://snyk.io/test/github/davesag/api-server-boilerplate/master/badge.svg)](https://snyk.io/test/github/davesag/api-server-boilerplate/master) | Latest Production Release |
94+
| `main` | [![CircleCI](https://circleci.com/gh/davesag/api-server-boilerplate/tree/main.svg?style=svg)](https://circleci.com/gh/davesag/api-server-boilerplate/tree/main) | [![codecov](https://codecov.io/gh/davesag/api-server-boilerplate/branch/main/graph/badge.svg)](https://codecov.io/gh/davesag/api-server-boilerplate) | [![Vulnerabilities](https://snyk.io/test/github/davesag/api-server-boilerplate/main/badge.svg)](https://snyk.io/test/github/davesag/api-server-boilerplate/main) | Latest Production Release |
9595

9696
### Prerequisites
9797

0 commit comments

Comments
 (0)