Skip to content

Conversation

@satazor
Copy link
Contributor

@satazor satazor commented Oct 29, 2023

The current implementation does not work with mono-repos:

  1. It assumes .git is in the cwd
  2. It doesn't allow filtering releases. In a mono-repo, there are different releases and tags per package (usually prefixed by the package name, like my-package@v1.0.0
  3. It doesn't allow filtering pull-requests by changes files, so that only pull-requests that affected a package are considered.

I've fixed 1 and implemented options for 2 and 3.

Example usage:

github-changelog-generator --future-release my-service@v0.1.0 --release-tag-prefix my-service@v

@satazor satazor force-pushed the feature/support-monorepos branch from 9d8dd83 to 02775b7 Compare October 29, 2023 01:00
@satazor satazor force-pushed the feature/support-monorepos branch from 02775b7 to eb1482b Compare October 29, 2023 01:15
@satazor satazor force-pushed the feature/support-monorepos branch 2 times, most recently from 63ffa59 to 88571e0 Compare October 29, 2023 12:41
@satazor satazor force-pushed the feature/support-monorepos branch from 88571e0 to 7a39247 Compare October 29, 2023 12:42
@satazor satazor force-pushed the feature/support-monorepos branch from 7a39247 to ab7c54e Compare October 29, 2023 12:54
@diogotorres97 diogotorres97 merged commit af86035 into master Nov 3, 2023
@diogotorres97 diogotorres97 deleted the feature/support-monorepos branch November 3, 2023 13:35
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.

3 participants