You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
URL: https://bugzilla.redhat.com/1557127
Creator: pkarampu at redhat
Time: 20180316T04:20:16
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:
The text was updated successfully, but these errors were encountered: