Skip to content

Conversation

manofscience8
Copy link

@manofscience8 manofscience8 commented Sep 4, 2025


Progress

  • Commit message must refer to an issue
  • Change must be properly reviewed (1 review required, with at least 1 Committer)

Errors

 ⚠️ OCA signatory status must be verified
 ⚠️ The pull request body must not be empty.

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jmc.git pull/671/head:pull/671
$ git checkout pull/671

Update a local copy of the PR:
$ git checkout pull/671
$ git pull https://git.openjdk.org/jmc.git pull/671/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 671

View PR using the GUI difftool:
$ git pr show -t 671

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/671.diff

@bridgekeeper bridgekeeper bot added the oca label Sep 4, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented Sep 4, 2025

Hi @manofscience8, 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 manofscience8" 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 4, 2025

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk
Copy link

openjdk bot commented Sep 4, 2025

⚠️ @manofscience8 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 b120bc4c54d11c2dd6160dfb5f3e76638c68efc7
$ 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.

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 3, 2025

@manofscience8 This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@manofscience8
Copy link
Author

manofscience8 commented Oct 5, 2025 via email

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

Labels

Development

Successfully merging this pull request may close these issues.

1 participant