Skip to content

Conversation

@DiegoTinitana
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Apr 13, 2020

Codecov Report

Merging #117 into master will increase coverage by 0.24%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #117      +/-   ##
==========================================
+ Coverage   92.30%   92.55%   +0.24%     
==========================================
  Files          37       37              
  Lines         403      403              
  Branches       23       23              
==========================================
+ Hits          372      373       +1     
+ Misses         26       25       -1     
  Partials        5        5              
Impacted Files Coverage Δ
...p/modules/time-clock/pages/time-clock.component.ts 89.70% <ø> (+1.47%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0775e94...9db7471. Read the comment docs.

- name: Setup Node.js
uses: actions/setup-node@v1
with:
node-version: 12
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

node version should be " node-version: '12.x' "

README.md Outdated

## Code scaffolding

## Commit format
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your text block is hurting the "code scaffolding" section please solve it.
I think your text block would fit better as another option of the menu "Prepare your environment".
Please change "Commit format" to "Commit message format"

@@ -0,0 +1,22 @@
name: Release
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's change it to:

bumping-versions-pipeline

README.md Outdated
## Code scaffolding

## Commit format
We are using format by release and tags: https://semver.org/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A commit message needs to start with one of the following words to bump the application version properly (This application is following a semver strategy for versioning https://semver.org/)

README.md Outdated
Comment on lines 58 to 60
- fix is equal to Patch Release example: 1.0.1
- feat is equal to Feature Release example: 1.1.0
- perf is equal to Breaking Release example: 2.0.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's mark the keywords in bold:

  • fix is equal to Patch Release example: 1.0.1
  • feat is equal to Feature Release example: 1.1.0
  • perf is equal to Breaking Release example: 2.0.0

package.json Outdated
"pattern": "^(#([0-9]+).*)",
"errorMessage": "Your commit message must start with issue number e.g. #39"
"pattern": "^(fix: #|feat: #|perf: #)[0-9].*",
"errorMessage": "Your commit should has this format> fix or feat or perf: #45 message"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your commit message needs to start with fix:, feat:, or perf: followed by issue number, e.g. fix: #43 any commit message

@DiegoTinitana DiegoTinitana force-pushed the 48-implement-semantic-version branch from b7bdedd to 23fa128 Compare April 13, 2020 21:27
@enriquezrene enriquezrene merged commit 1abbdf4 into master Apr 14, 2020
@enriquezrene enriquezrene deleted the 48-implement-semantic-version branch April 14, 2020 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants