Tickets :: Comment on [#10437] Test if package.xml is up-to-date on release

* Your Email Address
* Spam protection	Enter the letters below: .__ . ..__.. ..__. [__)\|_/ [__]\|\ \|\| \| [__)\| \\| \|\| \\|\|__\
Comment	>> When doing a release, check if an "update" command would change >> package.xml, > > Done. > >> show the diff to the user, > > Done. > >> and ask whether to apply this change or keep going with release process. > > I would expect the user to run "horde-components release --pretend" > before a release. horde-components will error out in that case and > display the reason for the problem. Even if you run "horde-components > release" without "--pretend" the script will error out immediately > and do nothing. > > In that case the problem can be resolved with a quick > "horde-components update --commit" which I wouldn't consider too much > of a burden. > > So while this could be done as an interactive process during the > release I didn't see a compelling reason for the additional effort.
Attachment
Watch this ticket