docs: suggests instead of prescribes source control strategy #124103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prescribing source control strategies based on potentialities which themselves aren't best practice is offensive to competent developers. Further, forcing each dev to create a file locally which can be committed wholly or as a template is massively inefficient. Consider Spring's application.properties file which also "may" contain secrets. It is common practice to commit such files to source control with placeholders for sensitive values instead of forcing the entire file to be created locally by each reviewer/contributor.
|
@JasonAndrewWakeman : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Learn Build status updates of commit 1d10964: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prescribing source control strategies based on potentialities which themselves aren't best practice is offensive to competent developers. Further, forcing each dev to create a file locally which can be committed wholly or as a template is massively inefficient. Consider Spring's application.properties file which also "may" contain secrets. It is common practice to commit such files to source control with placeholders for sensitive values instead of forcing the entire file to be created locally by each reviewer/contributor.