You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using simplified gitflow for my app (master = production, stage = testing and development). I merge development to stage and stage to production. I release versions on stage and master. New versions on master are normally some bug fixes thus new patch versions. New versions on stage can be all the types of versions.
I've recently ran into a situation where gitmoji-changelog acted weirdly for me.
Situation
master branch including version 1.12.5 and I've added a new bugfix 1.12.6
stage branch including version 1.12.5 and 1.13.0
Problem
I've tried to integrate the new version 1.12.6 to stage from master via both rebase and merge, but when releasing a new version 1.13.1 on stage gitmoji-changelog duplicated all the changes from 1.13.0 to the changelog of version 1.13.1 too.
I've tried several approaches when moving 1.12.6 from master to stage. Rebase and put changelog of 1.12.6 between already created changelogs of 1.12.5 and 1.13.0. Rebase and put changelog of 1.12.6 after 1.13.0. Merge and put between, merge and put after. But no matter what, every time I then created a new 1.13.1 version, its generated changelog included changes from 1.13.0.
Question
Is there any recommended way how to approach these situations? In the end, the only solution for me was manually delete all the duplicates so 1.13.1 includes only its changes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using simplified gitflow for my app (
master= production,stage= testing anddevelopment). I mergedevelopmenttostageandstagetoproduction. I release versions onstageandmaster. New versions onmasterare normally some bug fixes thus new patch versions. New versions onstagecan be all the types of versions.I've recently ran into a situation where gitmoji-changelog acted weirdly for me.
Situation
masterbranch including version1.12.5and I've added a new bugfix1.12.6stagebranch including version1.12.5and1.13.0Problem
I've tried to integrate the new version
1.12.6tostagefrommastervia both rebase and merge, but when releasing a new version1.13.1onstagegitmoji-changelog duplicated all the changes from1.13.0to the changelog of version1.13.1too.I've tried several approaches when moving
1.12.6frommastertostage. Rebase and put changelog of1.12.6between already created changelogs of1.12.5and1.13.0. Rebase and put changelog of1.12.6after1.13.0. Merge and put between, merge and put after. But no matter what, every time I then created a new1.13.1version, its generated changelog included changes from1.13.0.Question
Is there any recommended way how to approach these situations? In the end, the only solution for me was manually delete all the duplicates so
1.13.1includes only its changes.Beta Was this translation helpful? Give feedback.
All reactions