-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[JS] Ref #15952 make toOpenArray works better #17001
Conversation
@Araq I added a label |
That's for @narimiran to decide as he is doing the backports. |
I've removed the backport label from this PR in light of #17006 (but the label itself is still useful IMO, to tag whether or not to backport PR's) |
The label is useful but more useful would be "backport-1.2" etc. |
done, added those; only 1 need to be specified each time a backport is needed: It looks like this PR was backported to 1.4.4, but we may need to revisit this for 1.4.6 because of #17006
|
Please continue to use commit messages containing These labels might be easier for y'all to tag, but harder for me to do backports. I'm removing them so we don't have stuff labeled, but without tag. |
the problem with commit messages is that it requires the decision to be made before the PR is merged; a label gives you more flexibility and hindsight since you can tag/untag after a PR is merged; in this case for example, it was discovered after the PR was merged that it causes an issue and probably shouldn't have been backported. |
Sure but @narimiran is doing the work so we have to adapt. However, maybe there could be an official backport queue instead that lists commits to backport? |
* ref 15952 toOpenArray works in JS * fix
…ray.nim (nim-lang#17006) * followup nim-lang#17001: improve coverage for tests/openarray/topenarray.nim
What's the followup needed label for? |
ref #15952 toOpenArray works better