-
-
Notifications
You must be signed in to change notification settings - Fork 253
-
I'm working on a repository which is a fork of an existing (and still active) project. My fork is standalone, and is not intended to commit back to the upstream. As such, I want to generate a changelog of my changes, and only my changes. Without the changelog including any of the previous or new commits from the upstream repo which I pull down from time to time.
Looking at the documentation, I'm not sure how this is easily achieved?
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment 2 replies
-
which I pull down from time to time
This doesn't give enough information about your topology to answer your question. Are you rebasing the commits in your fork on the upstream project or merging from upstream into your fork or cherry picking commits you want or what? Do you have tags? What is their relation to the upstream project's tags?
Beta Was this translation helpful? Give feedback.
All reactions
-
Are you rebasing the commits in your fork on the upstream project or merging from upstream into your fork or cherry picking commits you want or what?
I merge upstream into my fork as a normal merge commit. I don't squash or rebase.
Do you have tags?
I do, each release is tagged. But the original project also makes use of tags, and often there are multiple tags from the orginal project between each of my releases.
What is their relation to the upstream project's tags?
Original project: v1.xx.xx
My fork: v2.xx.xx
Beta Was this translation helpful? Give feedback.
All reactions
-
git-cliff will work in this case. You can filter the commits by author to include only your changes.
Relevant links:
Beta Was this translation helpful? Give feedback.