Closed striezel closed 2 years ago
Thanks for the feedback.
I've removed the CI stuff from the release notes.
In fact, I have made the mistake myself merging #665 - this note should be removed.
Should this be a separate PR or should it be handled here, too? In the latter case, there might probably be a merge conflict when merging from develop
to master
.
@striezel I've just reverted the RELEASES.md
change in https://github.com/boostorg/gil/commit/616cf28e87618663fe57112f77e2b3f5b6bb23b8
Thanks for the merge.
Just a few minutes more and you would have been able to merge the whole release notes at once. :D But now it's another PR: #672. I probably should have communicated that I was working on the rest of those release notes, too.
I've just reverted the RELEASES.md change in https://github.com/boostorg/gil/commit/616cf28e87618663fe57112f77e2b3f5b6bb23b8
Alright.
No problem, baby steps 😊
GitHub allows to mark PR as draft, but I'm not sure if you can access that option?
If not, then simply prefix the subject with WIP:
until it's ready to be reviewed and merged.
GitHub allows to mark PR as draft, but I'm bot sure if you can access that option?
No, I do not have that option here, but I can change the PR's title.
I've just learned "Convert to draft" is available only to those with write access to a repo: https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/ - that is about changing stage of existing PR.
But, AFAIU, everyone should be able to create a draft pull request: https://github.blog/2019-02-14-introducing-draft-pull-requests/
Anyway, `WIP:'-ing a PR or creating a draft will work for us.
Description
Includes changes up to commit 25 (hash 434e78f76) from the table shown in https://github.com/boostorg/gil/issues/667.
References
See #667.
Tasklist