view contrib/vagrant/Vagrantfile @ 48979:9120c0cd935c stable

unamend: abort if commit was not created by `hg [un]amend` `hg unamend` can currently undo any kind of rewrite, as long as it has an obsmarker. However, that has quite unexpected results if you run it after e.g. `hg rebase` (expecting it to behave like a generic `hg undo` command), because it updates to the predecessor and leaves the old changes in the working copy. I think it's better to allow `hg unamend` only after `hg amend` (and after `hg unamend` because that's documented as being supported). Differential Revision: https://phab.mercurial-scm.org/D12390
author Martin von Zweigbergk <martinvonz@google.com>
date Mon, 21 Mar 2022 14:21:10 -0700
parents 7fd16ddabaa0
children
line wrap: on
line source

# -*- mode: ruby -*-

Vagrant.configure('2') do |config|
  # Debian 10.1 x86_64 without configuration management software
  config.vm.box = "debian/buster64"
  config.vm.hostname = "tests"

  config.vm.define "tests" do |conf|
    conf.vm.provision :file, source: "run-tests.sh", destination:"run-tests.sh"
    conf.vm.provision :shell, path: "provision.sh"
    conf.vm.synced_folder "../..", "/hgshared"
  end
end