Bug 1557127

Summary:	github issue update on spec commits
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	bugs, gluster-infra
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Process-Automation
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 12:52:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pranith Kumar K 2018-03-16 04:20:16 UTC

Description of problem:
I think most of the developers are used to seeing an update on the issue when a patch is sent on it, referring to it. At the moment for spec patches, the behaviour seems to be that we get the update after the commit is merged. Could we change this to be similar to what happens on FS? i.e. we get an update on the github issue as soon as a patch is sent.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Worker Ant 2020-03-12 12:52:12 UTC

This bug is moved to https://github.com/gluster/project-infrastructure/issues/27, and will be tracked there from now on. Visit GitHub issues URL for further details