RN for https://pagure.io/fedora-docs/release-notes/issue/416
rebased onto 7978844bd42c05a8a69673bd8b4ac5bb8936be1e
Damn, that took me a while to figure out :)
I'll go ahead and merge this, but in the future, please make sure to always check out the current release branch (f32) when you start working on a new release note. It seems that you didn't do that, and instead created the branch for this PR from branch issue426_package-changes, which you created for issue #426 - and I already merged that one. Since you created the branch for this PR from another topic branch, the resulting PR included both branches, not just the one you wanted. This time it didn't cause any problems, and even if it did I can fairly easily fix that, but it's still better to avoid this situation entirely and make sure to go back to the start and check out f32 before you start working on anything new.
f32
issue426_package-changes
Pull-Request has been merged by pbokoc
Ah! Apologies, for the incorrect branch. Sorry about the trouble caused. Thanks for fixing it! I will take care next time.
Regards
Shweta
On Tue, Apr 7, 2020 at 5:24 PM Petr Bokoc pagure@pagure.io wrote:
pbokoc commented on the pull-request: Issue 416 that you are following: `` Damn, that took me a while to figure out :) I'll go ahead and merge this, but in the future, please make sure to always check out the current release branch (f32) when you start workin= g on a new release note. It seems that you didn't do that, and instead created the branch for this PR from branch issue426_package-changes, which you created for issue #426 - and I already merged that one. Since y= ou created the branch for this PR from another topic branch, the resulting P= R included both branches, not just the one you wanted. This time it didn't cause any problems, and even if it did I can fairly easily fix that, but it's still better to avoid this situation entirely and make sure to go ba= ck to the start and check out f32 before you start working on anything new= . `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-docs/release-notes/pull-request/463
pbokoc commented on the pull-request: Issue 416 that you are following: `` Damn, that took me a while to figure out :)
Issue 416
I'll go ahead and merge this, but in the future, please make sure to always check out the current release branch (f32) when you start workin= g on a new release note. It seems that you didn't do that, and instead created the branch for this PR from branch issue426_package-changes, which you created for issue #426 - and I already merged that one. Since y= ou created the branch for this PR from another topic branch, the resulting P= R included both branches, not just the one you wanted. This time it didn't cause any problems, and even if it did I can fairly easily fix that, but it's still better to avoid this situation entirely and make sure to go ba= ck to the start and check out f32 before you start working on anything new= . ``
To reply, visit the link below or just reply to this email https://pagure.io/fedora-docs/release-notes/pull-request/463
--=20
Shweta Naresh
Technical Writer 3, Customer Content Services
Red Hat Czech Republic https://www.redhat.com
sjalgaon@redhat.com IM: shweta https://www.redhat.com
RN for https://pagure.io/fedora-docs/release-notes/issue/416