-
Notifications
You must be signed in to change notification settings - Fork 98
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
[release 4.7] Bug 1913343: Added changelog file #300
[release 4.7] Bug 1913343: Added changelog file #300
Conversation
I think that it is fine, but don't we want to autogenerate this CHANGELOG file? We could get this information from the PR template. |
@rluders, I think not all the changes should be in changelog file, but only sufficient ones. We probably need to discuss that after holidays :) |
It should be |
@rluders is there some way how to autogenerate it? I agree with Sergey that we don't want everything in the changelog, but maybe it would be still possible to generate it somehow. |
@tremes yep. It is possible to autogenete the changelog. I guess that we could even put some rules to WHAT should be included. Let me check it. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Sergey1011010, tremes The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@Sergey1011010: This pull request references Bugzilla bug 1913343, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@Sergey1011010: This pull request references Bugzilla bug 1913343, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@Sergey1011010: This pull request references Bugzilla bug 1913343, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@Sergey1011010: This pull request references Bugzilla bug 1913343, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@Sergey1011010: All pull requests linked via external trackers have merged: Bugzilla bug 1913343 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Added a changelog file not including minor changes and changes before October 27.
Categories
Sample archive
No changes
Documentation
No changes
Unit Tests
No new unit tests
Privacy
Not necessary
References
https://issues.redhat.com/browse/CCXDEV-3621
https://bugzilla.redhat.com/show_bug.cgi?id=1913343
https://access.redhat.com/solutions/???