88f796435d
* Before merging an item we set the remote ref to point to the current branch HEAD. * Instead of deleting the 'origin' remote in the executor we just set it to a bogus value. This feature enables jobs to perform quality checks on a per commit basis (e.g. commit message checks). For pull requests it was not possible before to determine which commits are part of the current change. Change-Id: I5de51917fbdfaa6ffee21dff7b63c520706c59eb
10 lines
374 B
YAML
10 lines
374 B
YAML
---
|
|
features:
|
|
- |
|
|
Git repositories will have a ``origin`` remote with refs pointing to the
|
|
previous change in the speculative state.
|
|
|
|
This allows jobs to determine the commits that are part of a change, which
|
|
was not possible before. The remote URL is set to a bogus value which
|
|
won't work with git commands that need to talk to the remote repository.
|