Skip to content

Episode #2 definitions needed for flag and message and -m #26

@deafeningraisins

Description

@deafeningraisins

There are some definition problems for newbies n the section that reads:
We can also see the commit message ‘Add index.md’, which we added by adding the -m flag to git commit. The commit message is used to record a short, descriptive, and specific summary of what we did to help us remember later on without having to look at the actual changes. If we just run git commit without the -m option, Git will launch nano (or whatever other editor we configured as core.editor) so that we can write a longer message.

The "flag" term doesn't mean what I might be used to. A flag is something that changes what a default action might ordinarily be, as is implied here. Flag needs to be defined for non-technical types. In most of my experience (usually email), it refers to a mark made for later action.
"Message" is ambiguous. From a non-technical perspective, I can't tell if that means I just created a text message in the index.md file or something else (maybe like doing some sort of vi editor). Based on what I've been told it's sort of like commenting out to document program changes.
-m means that your merging the old file with the new changes you made, though you're not saving the merged file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood issue for first-time contributors

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions