git ubuntu split-changelog

Bug #1709307 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
git-ubuntu
New
Wishlist
Unassigned

Bug Description

[13:30] <cpaelzer> rbasak: nacc: for deconstruction/logical we always split content from changelog changes
[13:30] <cpaelzer> for many trivial changes I found myself splitting those
[13:31] <cpaelzer> would it be a reasonable bug/feature-request to import those separate
[13:31] <cpaelzer> to always get a commit for d/changelog and another one for everything else?
[13:33] <rbasak> Maybe git ubuntu merge could do that for you?
[13:33] <rbasak> That seems reasonable. As it needs splitting out anyway.
[13:33] <rbasak> (in our workflow)
[13:59] <cpaelzer> rbasak: but people (e.g. myself) might want to not merge or do anything else where having these split by default might be helpful
[13:59] <cpaelzer> rbasak: e.g. cherry picking a change onto somewhere else, but not the changelog as it will always be different
[14:00] <cpaelzer> that is why I'd have located that fucntion at the import stage and not later on e.g. at git ubuntu merge
[14:02] <rbasak> cpaelzer: I don't agree with having the importer do it. It feels like that would represent some derived state rather than the canonical state of Launchpad publications.
[14:03] <rbasak> cpaelzer: but I'd be fine with tooling that does the split later for anyone, including it not being in git ubuntu merge and somewhere more general instead if there are other use cases.
[14:04] <rbasak> It's a good idea that the step be automated - I just think it should be in the tooling for later local manipulation rather than the importer.
[14:07] <cpaelzer> like "git ubuntu split-changelog <committish>"
[14:07] <cpaelzer> I'll file a bug to hear nacc's opinion as well and not forget it

Up as feature request for further discussion.

Tags: workflow
Nish Aravamudan (nacc)
Changed in usd-importer:
importance: Undecided → Wishlist
Robie Basak (racb)
tags: added: workflow
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.