Skip to content
This repository was archived by the owner on Mar 6, 2022. It is now read-only.

Feature: implement @open-sauced/conventional-commit #19

Closed
1 task done
0-vortex opened this issue Nov 8, 2021 · 1 comment · Fixed by #20
Closed
1 task done

Feature: implement @open-sauced/conventional-commit #19

0-vortex opened this issue Nov 8, 2021 · 1 comment · Fixed by #20
Assignees
Labels
💡 feature A label to note if work is a feature 👀 needs triage released

Comments

@0-vortex
Copy link
Contributor

0-vortex commented Nov 8, 2021

Type of feature

Feature

Current behavior

we are using npm run push with npx cz to create our git conventional commits

Desired solution

implement @open-sauced/conventional-commit as soon as it's officially released

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@0-vortex 0-vortex added 💡 feature A label to note if work is a feature 👀 needs triage labels Nov 8, 2021
@0-vortex 0-vortex self-assigned this Nov 10, 2021
0-vortex added a commit to 0-vortex/semantic-release-conventional-config that referenced this issue Nov 10, 2021
github-actions bot pushed a commit that referenced this issue Nov 10, 2021
## [2.1.0](v2.0.4...v2.1.0) (2021-11-10)

### Features

* implement @open-sauced/conventional commit ([#20](#20)) ([0ce2853](0ce2853)), closes [#19](#19)
@github-actions
Copy link

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
💡 feature A label to note if work is a feature 👀 needs triage released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant