Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(CHANGELOG.md): add changelog #43

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
## Unreleased
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it should be titled like the main package json so 2.0-alpha


### Feat

- **create-turbo**: apply package-manager transform
- **create-turbo**: apply official-starter transform

### Fix

- add missing synchronize trigger
Comment on lines +3 to +10
Copy link
Collaborator

Choose a reason for hiding this comment

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

Oh well my bad on not looking into merge rules of the repo before merging my changes
This should have been one pointer saying:

chore: setup monorepo

I got rid of merge commits in favour of squash, so this won't happen in the future

Could you:

  • delete branch [release-v2.0.0](https://github.com/brainhubeu/license-auditor/tree/release-v2.0.0)
  • re-create it from main
  • set up a PR with cherry-picked commits from this PR: chore: setup monorepo #41 titled chore: setup monorepo
  • re-open this PR with new base

Sorry for this extra work, it was my mess up


## v1.2.0 (2022-03-02)

## v1.1.1 (2021-10-08)
Comment on lines +12 to +14
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it possible to skip those since we're keeping a changelog starting from v2?

Loading