[nonextensible-applies-to-private] Adding private field to non-extensible object throws

[erights]

To be the test262 tests for the https://github.com/tc39/proposal-nonextensible-applies-to-private

See tc39/proposal-nonextensible-applies-to-private#5

Actual PR content by @o-

[ljharb]

(private fields, not private symbols)

[erights]

@ljharb PR title corrected.

@o- @ljharb , I tried to change the commit message to follow suit, but when I did a git push --force with the new commit message, I got

$ git push --force
ERROR: Permission to o-/test262.git denied to erights.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Outside of my patterns of habitual use, I know much less about git than I should. But I am surprised that I can have enough permission to change the PR's title and description (which I do understand is github's not git's) and not have enough permission to push.

I'll fork and redo under @erights if needed. But if could just be granted the needed permission or get advice on how else to proceed, that would be great. Thanks.

[erights]

What does this one CI error mean?

[ptomato]

@erights: re. the permission issue, you probably have the ability to change any PR or issue title throughout the TC39 organization just by virtue of being a delegate. The difference is that you don't automatically get permission to push code to someone else's personal space, which is what https://github.com/o-/test262 is. Likely @o- will have to add you as a "collaborator" which can be done in the settings.

re. the CI error, that is the ESMETA tool which executes the changed tests against the current edition of ECMAScript. It's expected to fail if you are writing a test for a stage <4 proposal.

[erights]

Closing in favor of #4577