chore: Add documentation on how to update the plugin#55
Merged
Conversation
AdrienClairembault
approved these changes
Dec 15, 2025
Contributor
|
done 
|
Contributor
|
waiting for another review |
Contributor
|
It is OK for me, but my approval generates a 500 error. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Since this repository is used by many plugin as template (as it's goal), I don't have the permission to edit it but we should declare it as a template repository
This PR update the README to also explain the user how he can then update his repo in the future when the template evolves.
This use the template-sync script, symfony-docker is using it for example