8382090: Remove .rej and .orig from .gitignore#30772
8382090: Remove .rej and .orig from .gitignore#30772Domest0s wants to merge 1 commit intoopenjdk:masterfrom
Conversation
|
👋 Welcome back Domest0s! A progress list of the required criteria for merging this PR into |
|
@Domest0s This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 29 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@aivanov-jdk, @erikj79, @sendaoYan, @liach) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
aivanov-jdk
left a comment
There was a problem hiding this comment.
Looks good to me.
I agree that seeing .rej and .orig files is important, especially in update releases. If a patch doesn't apply cleanly, the .rej files provide crucial information about the conflicts.
These file types were added to .gitignore in #25474 (JDK-8357920) to prevent them from being committed into the repo. Yet I think seeing both .rej and .orig in the output of git status outweighs rare occasions when these files could accidentally be committed.
SKARA-2514 will ensure .rej and .orig can't be committed.
|
@erikj79 @aivanov-jdk Thank you for the review. |
|
/integrate |
|
/sponsor |
|
Going to push as commit 35f623b.
Your commit was automatically rebased without conflicts. |
|
@sendaoYan @Domest0s Pushed as commit 35f623b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Keeping
.rejand.origfiles visible to the developer is important. It helps minimizing human error when moving or applying source code changes.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/30772/head:pull/30772$ git checkout pull/30772Update a local copy of the PR:
$ git checkout pull/30772$ git pull https://git.openjdk.org/jdk.git pull/30772/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 30772View PR using the GUI difftool:
$ git pr show -t 30772Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/30772.diff
Using Webrev
Link to Webrev Comment