Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
FAQ.adullact.org
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Value stream analytics
Contributor 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
Adullact
FAQ.adullact.org
Commits
dfae93b8
Commit
dfae93b8
authored
3 years ago
by
Fabrice Gangler
Browse files
Options
Downloads
Patches
Plain Diff
DOC(dev): improve 21_hugo-theme_update-git-submodule.md
parent
79264199
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Documentation/doc_for-developer/21_hugo-theme_update-git-submodule.md
+15
-15
15 additions, 15 deletions
...n/doc_for-developer/21_hugo-theme_update-git-submodule.md
with
15 additions
and
15 deletions
Documentation/doc_for-developer/21_hugo-theme_update-git-submodule.md
+
15
−
15
View file @
dfae93b8
...
...
@@ -16,21 +16,21 @@ git submodule update --remote
git commit
-m
"CHORE: update submodule ref"
```
>
We strongly recommend to follow the following examples
>
for the commit message and the merge request :
>
>
- [commit example](https://gitlab.adullact.net/adullact/faq.adullact.org/-/commit/2623374c462c403447d564e6738050df417789dc)
>
- Add a link to old commit used for theme sub-module before update
>
- Add a link to new commit used for theme sub-module after update
>
- Add BREAKING CHANGE footer with a message for developers:
>
`BREAKING CHANGE: update Git submodule on your local repository`
>
- [Merge request example](https://gitlab.adullact.net/adullact/faq.adullact.org/-/merge_requests/146)
>
- Add a link to old commit used for theme sub-module before update
>
- Add a link to new commit used for theme sub-module after update
>
- Add a message for developers : "To do : after the merge of the MR ..."
>
- Add **breaking-change** label
>
>
This allows a quick verification of change made.
We
**
strongly
**
recommend to follow the following examples
for the commit message and the merge request :
-
[
commit example
](
https://gitlab.adullact.net/adullact/faq.adullact.org/-/commit/2623374c462c403447d564e6738050df417789dc
)
-
Add a link to old commit used for theme sub-module before update
-
Add a link to new commit used for theme sub-module after update
-
Add BREAKING CHANGE footer with a message for developers:
>
`BREAKING CHANGE: update Git submodule on your local repository`
-
[
Merge request example
](
https://gitlab.adullact.net/adullact/faq.adullact.org/-/merge_requests/146
)
-
Add a link to old commit used for theme sub-module before update
-
Add a link to new commit used for theme sub-module after update
-
Add a message for developers : "To do : after the merge of the MR ..."
-
Add
**breaking-change**
label
This allows a quick verification of change made.
## To do after the update Git submodule of theme on main repository
...
...
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