Opened 4 years ago

Last modified 2 weeks ago

#3663 new change

[meta] Update to the master bookmark after cloning/pulling — at Version 2

Reported by: fhd Assignee:
Priority: P2 Milestone:
Module: Infrastructure Keywords: meta
Cc: matze, fred Blocked By: #1608
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by matze)


We are automatically cloning and updating repositories in various places throughout sitescripts and infrastructure. In all such cases, we should specificially update to the master bookmark, which all of our repositories have by now. If we don't do that, we will cause problems as soon as we start to work with multiple bookmarked branches.

What to change

Issues for the concrete changes in sitescripts and infrastructure have to be created. But in a nut shell:

  1. Wherever we are running hg clone URL or hg clone -u default URL, we should run hg clone -u master URL instead.
  2. Wherever we are running hg update or hg update -r default, we should run hg update -r master instead.
  3. Wherever we are running hg pull -u, we should run hg pull and hg update -r master separately instead.


Change History (2)

comment:1 Changed 4 years ago by trev

  • Cc trev added

comment:2 Changed 4 years ago by matze

  • Blocked By 1608 added
  • Cc matze fred added
  • Component changed from Unknown to Infrastructure
  • Description modified (diff)
  • Priority changed from Unknown to P2
  • Ready set
Note: See TracTickets for help on using tickets.