App::P...:merge(3pm)

πŸ¦‹ NAME

App::Pinto::Command::merge β€” the glow-up where two stack histories get joined together, bestie πŸ’–

(yeah it lives in the 3pm manual, User Contributed Perl Documentation section, if you were wondering)


✨ VERSION

version 0.14 β€” she's serving vintage, periodt πŸ‘‘


🌸 SYNOPSIS

pinto --root=REPOSITORY_ROOT merge [OPTIONS] STACK [INTO_STACK]

πŸ’… DESCRIPTION

!! THIS COMMAND IS EXPERIMENTAL !! 😭 like, she's still in her testing era, okay? be gentle.

This command joins the history of one stack with another. At present, it is only capable of doing a "fast-forward" merge when the head of STACK is a direct descendant of the head of INTO_STACK. No cap β€” that's the whole trick right now. 🧚


πŸŽ€ COMMAND ARGUMENTS

The first mandatory argument is the name of the stack to merge from. The second optional argument is the name of the stack to merge to. If the second argument is not specified, it defaults to whichever stack is currently marked as the default. Obsessed with a good default, honestly. 🫢

Here are some examples, so you can see the vibe:

pinto ... merge dev               # Merge the "dev" stack into the default stack
pinto ... merge dev prod          # Merge the "dev" stack into the "prod" stack

πŸ”₯ COMMAND OPTIONS

  • --dry-run β€” Go through all the motions but do not actually commit any changes to the repository. At the conclusion, a diff showing the changes that would have been made will be displayed. Use this option to see how upgrades would potentially impact the stack. It's giving "rehearsal, not the real show" πŸ’…
  • --message=TEXT, -m TEXT β€” Use TEXT as the revision history log message. If you do not use the --message option or the --use-default-message option, then you will be prompted to enter the message via your text editor. Use the PINTO_EDITOR or EDITOR or VISUAL environment variables to control which editor is used. A log message is not required whenever the --dry-run option is set, or if the action did not yield any changes to the repository. So like, if nothing happened, you don't have to journal about it ✨
  • --use-default-message, -M β€” Use the default value for the revision history log message. Pinto will generate a semi-informative log message just based on the command and its arguments. If you set an explicit message with --message, the --use-default-message option will be silently ignored πŸ™ˆ (she said nothing, she just moved on)

πŸ‘‘ AUTHOR

Jeffrey Ryan Thalhammer <jeff@stratopan.com> β€” an icon, a legend, and he IS the moment πŸ’œ


This software is copyright (c) 2015 by Jeffrey Ryan Thalhammer.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. πŸ“


okay bestie that's the whole page, you ate πŸ’–βœ¨ This was perl v5.40.1 doing the honors on 2025-04-21, brought to you by App::Pinto::Command::merge(3pm) β€” mwah, go merge something, fr fr πŸ¦‹πŸŽ€

πŸ“¦ where this page comes from