Project

General

Profile

Actions
Copy link

Bug #7355

closed

On first run after creation, merge does not know about new branches

Added by Vincent MEMBRÉ about 9 years ago. Updated about 8 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Benoît PECCATTE
Category:
Rudder dev tools
Target version:
master
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When 'rudder-dev merge all' runs after a branch was created, he does not find the new branch on first run but only on the second run

Adding a fetch at the beginning of the run would fix the issue

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 9 years ago

  • Description updated (diff)
  • Category set to Rudder dev tools
  • Assignee set to Vincent MEMBRÉ
  • Priority changed from N/A to 1 (highest)
  • Target version set to master

Added description, due to a to fast enter typing ...

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 9 years ago

  • Status changed from New to In progress
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-tools/pull/100
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Benoît PECCATTE about 8 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF