Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Developer Documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
John Twyman
Developer Documentation
Commits
6c9bdc57
Commit
6c9bdc57
authored
5 months ago
by
ayduns
Browse files
Options
Downloads
Patches
Plain Diff
Update managed.md - spelling
parent
dc974212
No related branches found
Branches containing commit
No related tags found
Tags containing commit
Loading
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/extensions/managed.md
+2
-2
2 additions, 2 deletions
docs/extensions/managed.md
with
2 additions
and
2 deletions
docs/extensions/managed.md
+
2
−
2
View file @
6c9bdc57
...
...
@@ -27,10 +27,10 @@ The recommended way to package and distribute managed records is using the [`civ
-
**always:**
Forcibly overwrite record with values from the
`.mgd.php`
definition with every cache-flush.
-
**never:**
Once installed, the record will never be updated.
-
**unmodified:**
Updates to the
`.mgd.php`
will be prop
i
gated only if the record has not been updated by the user.
-
**unmodified:**
Updates to the
`.mgd.php`
will be prop
a
gated only if the record has not been updated by the user.
In general,
`always`
is a good choice for records which are not meant to be updated by the user, such as reserved
`OptionValues`
.
In most other cases,
`unmodified`
is the best trade-off between allowing edits to be made by the user, and prop
id
ating updates
In most other cases,
`unmodified`
is the best trade-off between allowing edits to be made by the user, and prop
ag
ating updates
when changes are made to the
`.mgd.php`
in new versions of the extension. Changes made by the user can be undone
by the
[
`revert`
](
../api/v4/actions.md#write-actions
)
API action.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment