Skip to content

Conversation

@kabutz
Copy link
Contributor

@kabutz kabutz commented Sep 29, 2020

Probably a small typo during refactoring from only calling one toArray() method to a whole array of toArray()s.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed

Error

 ⚠️ OCA signatory status must be verified

Download

$ git fetch https://git.openjdk.java.net/jdk pull/400/head:pull/400
$ git checkout pull/400

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Sep 29, 2020
@bridgekeeper
Copy link

bridgekeeper bot commented Sep 29, 2020

Hi @kabutz, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user kabutz" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@openjdk
Copy link

openjdk bot commented Sep 29, 2020

⚠️ @kabutz a branch with the same name as the source branch for this pull request (master) is present in the target repository. If you eventually integrate this pull request then the branch master in your personal fork will diverge once you sync your personal fork with the upstream repository.

To avoid this situation, create a new branch for your changes and reset the master branch. You can do this by running the following commands in a local repository for your personal fork. Note: you do not have to name the new branch NEW-BRANCH-NAME.

$ git checkout -b NEW-BRANCH-NAME
$ git branch -f master 86491a5f6b2958480a73183b9a4a29ef55d3a569
$ git push -f origin master

Then proceed to create a new pull request with NEW-BRANCH-NAME as the source branch and close this one.

@openjdk
Copy link

openjdk bot commented Sep 29, 2020

@kabutz The following label will be automatically applied to this pull request:

  • core-libs

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-libs [email protected] oca Needs verification of OCA signatory status

Development

Successfully merging this pull request may close these issues.

1 participant