question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support adding release branch changes to master's changelog

See original GitHub issue

Hi!

For the https://github.com/mozilla-neutrino/neutrino-dev repository, after we released v8.2.0, we switched to treating master as the next breaking release (v9; as yet unreleased), and have since released a v8.2.1 and v8.2.2 from a separate release/v8 branch.

auto-changelog successfully updated CHANGELOG.md in that branch (run via a package.json version entry), however I’ve tried to find a way to update master’s changelog (since that’s what people will look at when visiting the repository on GitHub), and can’t find a way to do so.

It seems like as-is, when we release v9 the master changelog and will end up skipping straight from v8.2.0 to v9.x.x.

Is this something that’s possible to achieve at the moment? If not, what changes do you think might be required to do so?

Many thanks 😃

cc @eliperelman

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
cookpetecommented, May 17, 2018

@edmorley I’ve added my attempt at an --include-branch option to 1.6.0. Would be great to see if it’s at all useful for your use case (or if it even works properly) as I don’t have any decent repos to test it with.

0reactions
edmorleycommented, Jun 28, 2018

Sorry for the delayed reply – I’ve finally had a chance to try this out (mozilla-neutrino/neutrino-dev#970), and it works great. Many thanks!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Generating release changelog from non-master branch ...
The release notes for the latest major release are generated and include all the commits from master branch, but if I want to...
Read more >
Gitflow release branch process from start to finish example
The Gitflow release branch is made from the develop branch and gets merged into both master and develop when finished. Gitflow release branch...
Read more >
Support for renaming an existing branch | GitHub Changelog
This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch.
Read more >
Get changes from master into branch in Git - Stack Overflow
It seems I was a little off in my question, I branched from a branch then made changes to the original branch. If...
Read more >
Using a Branching Strategy That Works - Cocoacasts
The answer is simple. You create a hotfix branch from master , apply the solution, and release the hotfix. After releasing the hotfix,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found