Skip to content

Commit

Permalink
chore: rename master branch to main
Browse files Browse the repository at this point in the history
  • Loading branch information
lpatiny committed Feb 2, 2024
1 parent 8adb8f1 commit b98ada9
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 4 deletions.
3 changes: 1 addition & 2 deletions .github/workflows/nodejs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,12 @@ name: Node.js CI
on:
push:
branches:
- master
- main
pull_request:

jobs:
nodejs:
# Documentation: https://github.com/zakodium/workflows#nodejs-ci
uses: zakodium/workflows/.github/workflows/nodejs.yml@nodejs-v1
with:
node-version-matrix: '[14, 16]'
test-setup-command: 'npm run build && node dist/ml.js && node dist/ml.min.js'
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: Release
on:
push:
branches:
- master
- main

jobs:
release:
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ parameter is the object returned by an earlier call of `toJSON`.

## Commit Guidelines

The rules are based on the [AngularJS commit guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit). This leads to **more readable messages** that are easy to follow when looking through the **project history**.
The rules are based on the [AngularJS commit guidelines](https://github.com/angular/angular.js/blob/main/CONTRIBUTING.md#commit). This leads to **more readable messages** that are easy to follow when looking through the **project history**.

### Commit Message Format
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
Expand Down

0 comments on commit b98ada9

Please sign in to comment.