Burak Yigit Kaya
Burak Yigit Kaya
@jharris4 thanks for digging more and sorry for the late response. Sounds like this may also be a duplicate of #2064 as #3905. What do you think?
@jharris4 https://yarnpkg.com/en/docs/nightly
@jharris4 can we close this now?
@jharris4 oh shoot. Are you still on Node 8.1?
@armcknight repeating my question from #415, why not go with the fully automated changelog approach so you don't even need the `# Unreleased` part and all the dance around that?
@armcknight It does much more than that if you are willing to use it. Here's a good example: https://github.com/getsentry/craft/releases/tag/0.25.0 -- It uses GitHub milestones to group PRs and use a...
@armcknight the thing I was trying to point at was, if you were to use fully automated changelogs, the need for the `Unreleased` section vanishes as there won't be anyone...
I'm not on the team but I think this is a pretty good idea ☺️ Suggestions: 1. Just name it `tags` 2. Deprecate the `tagPrefix` config and roll it into...
Sounds good to me. An alternative might be to allow tagPrefix to be an array of strings (new behavior) or just a string. This is a bit "dirty" but allows...
If we had an early warning system, I think having the current behavior in place might have been useful. Currently, it just made things worse as far as I can...