Skip to content

Commit

Permalink
fix: pushing the tags and commits is necessary (#173)
Browse files Browse the repository at this point in the history
## PR Checklist

Please check if your PR fulfills the following requirements:

- [ ] The commit message follows our guidelines: CONTRIBUTING.md#commit
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)

## PR Type

What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->

```
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
```

## What is the current behavior?

We are not pushing the tags and commits after creating the changelog
which causes an error on the GitHub release post actions

## What is the new behavior?

We push always to GitHub
  • Loading branch information
NachoVazquez authored Aug 16, 2023
1 parent 0e2cd7b commit 8ad9046
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion packages/ngworker/lumberjack/project.json
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@
"preset": "conventional",
"tagPrefix": "v",
"noVerify": true,
"push": false,
"push": true,
"preid": "beta",
"syncVersions": false,
"commitMessageFormat": "release(${projectName}): 🎸 cut release to ${version}",
Expand Down

0 comments on commit 8ad9046

Please sign in to comment.