Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lammps
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
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
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
multiscale
lammps
Commits
4f45d39a
Commit
4f45d39a
authored
8 years ago
by
Richard Berger
Browse files
Options
Downloads
Patches
Plain Diff
Add warning formatting
Any paragraph starting with IMPORTANT NOTE: is transformed into a warning.
parent
7d057d4c
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
doc/src/tutorial_github.txt
+8
-10
8 additions, 10 deletions
doc/src/tutorial_github.txt
with
8 additions
and
10 deletions
doc/src/tutorial_github.txt
+
8
−
10
View file @
4f45d39a
...
@@ -111,16 +111,14 @@ After everything is done, add the files to the branch and commit them:
...
@@ -111,16 +111,14 @@ After everything is done, add the files to the branch and commit them:
$ git add doc/src/tutorial_github.txt
$ git add doc/src/tutorial_github.txt
$ git add doc/src/JPG/tutorial_*.png :pre
$ git add doc/src/JPG/tutorial_*.png :pre
[Warning]
IMPORTANT NOTE: Do not use `git commit -a`. The -a flag will automatically
include _all_ modified or new files and that is rarely the behavior you want.
{Do not use `git commit -a`. The -a flag will automatically include
It can easily create to accidentally adding unrelated and unwanted changes into
_all_ modified or new files and that is rarely the behavior you want.
the repository. It is highly preferable to explicitly use `git add`, `git rm`,
It can easily create to accidentally adding unrelated and unwanted
`git mv` for adding, removing, renaming files, respectively, and then `git
changes into the repository. It is highly preferable to explicitly
commit` to finalize the commit. If you find doing this on the command line too
use `git add`, `git rm`, `git mv` for adding, removing, renaming files,
tedious, consider using a GUI, the one included in git distributions written in
respectively, and then `git commit` to finalize the commit. If you
Tk, i.e. use `git gui`.
find doing this on the command line too tedious, consider using a GUI,
the one included in git distributions written in Tk, i.e. use `git gui`.}
After adding all files, the change can be commited with some useful message
After adding all files, the change can be commited with some useful message
that explains the change.
that explains the change.
...
...
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