Replies: 1 comment
-
We have created our own plugin in the end. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
(This is a copy of StackOverflow question I posted)
We have somehow extended commit messages syntax to cover internal changes that should be helpful for some departments in the company but we don't want to share them with public. For example apart from the well known
fix
we have internal siblingifix
.I am struggling to generate "Internal Changelog" that includes all (relevant) commits and public Changelog that contains reduced set of info.
I tried to setup the
releaserc.yml
to run@semantic-release/changelog
twice with different config:However this seem to pickup only the first config and even though
INTERNAL_CHANGELOG.md
is created they both are the same - containing only the commits targeted to public.Another attempt was to have 2 sets of
.releaserc.yml
in CI file variables, run 2 jobs in sequence and before the job starts copy the relevant config. One job would generate changelog and the other internal one. The problem I ran into there was that the first one tagged the version in GitLab and therefore the second job did not find any relevant commits.How would you deal with generating 2 sets of changelog, please?
Beta Was this translation helpful? Give feedback.
All reactions