zuul/zuul
Code Issues Proposed changes

Allow using remote refs to find commits for change

Browse Source 
* 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
This commit is contained in:
Simon Westphahl
2018-02-15 09:44:39 +01:00
parent f523b1679e
commit 88f796435d
6 changed files with 87 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
releasenotes/notes/git-remote-refs-71bd2fc2bb05155d.yaml Normal file
View File

@@ -0,0 +1,9 @@
---
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.