Skip to content

Generated by liferay-continuous-integration #6536

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.

Sign up for GitHub

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

Open
liferay-continuous-integration wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Generated by liferay-continuous-integration #6536

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion test.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
##
## DO NOT EDIT THIS FILE.
## DO NOT DELETE THIS FILE.
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The change from DO NOT EDIT to DO NOT DELETE makes the comment less clear. The following lines explain how to update the properties by creating a separate file, which is an alternative to editing this one. Therefore, the original DO NOT EDIT instruction was more direct and relevant to the context of overriding properties. While deleting the file may also be undesirable, the primary action a developer would consider for updating properties is editing, which the original comment correctly advised against. Reverting this change would improve clarity for developers.

## DO NOT EDIT THIS FILE.

##
## To update the properties of this file, create a separate properties file
## named "test.${user.name}.properties" with the properties to overwrite.
Expand Down