Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug:1557127] github issue update on spec commits #27

Open
gluster-ant opened this issue Mar 12, 2020 · 0 comments
Open

[bug:1557127] github issue update on spec commits #27

gluster-ant opened this issue Mar 12, 2020 · 0 comments
Labels
Migrated The bugs migrated from bugzilla to Github Type:Bug

Comments

@gluster-ant
Copy link
Collaborator

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:

@gluster-ant gluster-ant added Migrated The bugs migrated from bugzilla to Github Type:Bug labels Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Migrated The bugs migrated from bugzilla to Github Type:Bug
Projects
None yet
Development

No branches or pull requests

1 participant