Foreground

🧠 BRAIN

brain

CAUTION

Some files are private or not ready yet, if a link gives you a 404 that's why :)
This is a work in progress, new notes will be added daily

List of note Indexes

🔒 PROJECTS
🌐 ART
🌐 TECHNOLOGY
🔒 SCIENCE
🔒 PHILO-PSYCHO
🔒 HISTORY
🔒 HEALTH
🔒 GAMING
🌐 KNOWLEDGE


                .... |\| .|||.    |\/|  .|\\. .|.
              .\\||/|.  .\|..||  .\|..|||...||.....
            .|   .....||.|\\\\\\    ... |\\\/. .\\. .||
        .\\|   .|\\|..|\\ .\\\\  .\\|. .\\\\\|  |\| |\\|
        |\\  |\\|..  /\\\. |\|\\   \\\\|.   .|\\. .\\\\|
        .\\. |\\\\\\\|.. .\\|      .\\||\\/|. |\\|     .|/\|
      \. .\\\||/\|....   \\| |\/   |\\\  |\\\| .\\|  \\| ....
    |\/  |\\| |\\\\\\\| |\|.\\\   \\\\. |\\\\| |\\  \\.  ||..
      ..|||\|  .. .\\\\. |\\\\\\  .\\|....|\\\. |\\\\\\  |/. |/
    \\\|..   .\\\ |\\. .\\\| \\|   |||\\\.  ...|\\/||.  .\\\
  |\|  |\/.  /\\\\\| .\\\\. \\.   .../|.   .|\\\|.   |\\\|  |\\
    .  |||\\|.  ..||| .\\|.  |\|  \\|..../\\| |\\|  .\\\\\   ..
    \\|  .||\|.|..      |\\\|./\  \\||\. ||...    .\\\\/.  |\/||
    ..|/||.   |\\\\\|.     .|/\|  ||.        .||\\\     .|||. |\
  .\/|  \\\. .|\\\|||\\\||..       .|\\\\\\\|\\\\.  /\\\\||. |
    .|| |\\\\|  .......|\\\\\\.  .\\\. ..|||....  .\\\\|.. ...
    \\||....|\\\\\\\\||\\\\\\\/   |\|....|||\\\\\\\/....|\\\|
      ||.|\||\\| .....|\\\\..\\|    .|\\\. ||........ .|\|...
          . |\  /\\/\\\\\\. |\.  .\\\\\\.  ./\\\\/  |\\\||.
        .|\.|\| .|\|... ..              ./\\|..|\\|  ..
            .|\\|  .\\\\.\\\\\\\   \||...\\\|..|\\\|.||
                |\. ..||....||     ... ..||\\\. .|.
                        ...            .......

loading from brain

🧠 BRAIN
created:
updated:

error

Outgoing

CAUTION

Using these links might break the site. WIP

🧠 BRAIN

List of note Indexes

Tags

Outgoing

Conventional Commits 1.0.0

Summary

Examples

Commit message with description and breaking change footer

Commit message with `!` to draw attention to breaking change

Commit message with scope and `!` to draw attention to breaking change

Commit message with both `!` and BREAKING CHANGE footer

Commit message with no body

Commit message with scope

Commit message with multi-paragraph body and multiple footers

Specification

Why Use Conventional Commits

FAQ

How should I deal with commit messages in the initial development phase?

Are the types in the commit title uppercase or lowercase?

What do I do if the commit conforms to more than one of the commit types?

Doesn’t this discourage rapid development and fast iteration?

Might Conventional Commits lead developers to limit the type of commits they make because they’ll be thinking in the types provided?

How does this relate to SemVer?

How should I version my extensions to the Conventional Commits Specification, e.g. `@jameswomack/conventional-commit-spec`?

What do I do if I accidentally use the wrong commit type?

When you used a type that’s of the spec but not the correct type, e.g. `fix` instead of `feat`

When you used a type not of the spec, e.g. `feet` instead of `feat`

Do all my contributors need to use the Conventional Commits specification?

How does Conventional Commits handle revert commits?

List of note Indexes

Tags

Outgoing

Conventional Commits 1.0.0

Summary

Examples

Commit message with description and breaking change footer

Commit message with ! to draw attention to breaking change

Commit message with scope and ! to draw attention to breaking change

Commit message with both ! and BREAKING CHANGE footer

Commit message with no body

Commit message with scope

Commit message with multi-paragraph body and multiple footers

Specification

Why Use Conventional Commits

FAQ

How should I deal with commit messages in the initial development phase?

Are the types in the commit title uppercase or lowercase?

What do I do if the commit conforms to more than one of the commit types?

Doesn’t this discourage rapid development and fast iteration?

Might Conventional Commits lead developers to limit the type of commits they make because they’ll be thinking in the types provided?

How does this relate to SemVer?

How should I version my extensions to the Conventional Commits Specification, e.g. @jameswomack/conventional-commit-spec?

What do I do if I accidentally use the wrong commit type?

When you used a type that’s of the spec but not the correct type, e.g. fix instead of feat

When you used a type not of the spec, e.g. feet instead of feat

Do all my contributors need to use the Conventional Commits specification?

How does Conventional Commits handle revert commits?

Commit message with `!` to draw attention to breaking change

Commit message with scope and `!` to draw attention to breaking change

Commit message with both `!` and BREAKING CHANGE footer

How should I version my extensions to the Conventional Commits Specification, e.g. `@jameswomack/conventional-commit-spec`?

When you used a type that’s of the spec but not the correct type, e.g. `fix` instead of `feat`

When you used a type not of the spec, e.g. `feet` instead of `feat`