Skip to content

Kumpels-SAS/.github

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

2 Commits
Β 
Β 
Β 
Β 

Repository files navigation

Contributing

Making commits

Commit your changes when you are happy with them. But remember that a commit should only contain changes relevant to its message.

Summarize changes in around 50 characters or fewer.

More detailed explanatory text, if necessary, will be put on the body. Wrap it to about 72 characters or so, max 80.

The first line is treated as the title of the commit and the rest of the text as the body.

The blank line separating the summary from the body is critical (unless you omit the body entirely); various tools like log, shortlog and rebase can get confused if you run the two together.

The commit title must complete the phrase "If applied, this commit will …​", like this:

  • If applied, this commit will Refactor subsystem X for readability

  • If applied, this commit will Update getting started documentation

  • If applied, this commit will Remove deprecated methods

  • If applied, this commit will Release version 1.0.0

  • If applied, this commit will Merge pull request #123 from user/branch

Explain the problem that this commit is solving. Focus on why you are making this change as opposed to how (the code explains that). Are there side effects or other unintuitive consequences of this change? Here’s the place to explain them.

Paragraphs will come after blank lines.

Bullet points are okay, too. Use an asterisk, preceded by a single space, with blank lines in between in case your items exceeds 80 chars.

Put references to the issue tracker at the bottom, like this:

Fix #123
See also #456, #789

Always follow these rules:

  • Use the present tense ("Add feature" not "Added feature")

  • Use the imperative mood ("Move cursor to…​" not "Moves cursor to…​")

  • Limit the first line to 72 characters or fewer

  • Reference issues and pull requests liberally after the first line

  • Capitalize when possible following grammar rules

  • Do not end the title line with a period

  • Do not assume everyone understands what the original problem was, ensure you add it

  • Do not think your code is self-explanatory

  • Start the commit message with the corresponding emoji (gitmoji):

Emoji Unicode Name Usage

🎨

ARTIST PALETTE

Improve structure / format of the code.

⚑

HIGH VOLTAGE SIGN

Improve performance.

πŸ”₯

FIRE

Remove code or files.

πŸ›

BUG

Fix a bug.

πŸš‘

AMBULANCE

Critical hotfix.

✨

SPARKLES

Introduce new features.

πŸ“

MEMO

Add or update documentation.

πŸš€

ROCKET

Deploy stuff.

πŸ’„

LIPSTICK

Add or update the UI and style files.

πŸŽ‰

PARTY POPPER

Begin a project.

βœ…

WHITE HEAVY CHECK MARK

Add, update or pass tests.

πŸ”’

LOCK

Fix security issues.

πŸ”

CLOSED LOCK WITH KEY

Add or update secrets.

πŸ”–

BOOKMARK

Release / Version tags.

🚨

POLICE CARS REVOLVING LIGHT

Fix compiler / linter warnings.

🚧

CONSTRUCTION SIGN

Work in progress.

πŸ’š

GREEN HEART

Fix CI build.

⬇️

DOWNWARDS BLACK ARROW VARIATION SELECTOR-16

Downgrade dependencies.

⬆️

UPWARDS BLACK ARROW VARIATION SELECTOR-16

Upgrade dependencies.

πŸ“Œ

PUSHPIN

Pin dependencies to specific versions.

πŸ‘·

CONSTRUCTION WORKER

Add or update CI build system.

πŸ“ˆ

CHART WITH UPWARDS TREND

Add or update analytics or track code.

β™»

BLACK UNIVERSAL RECYCLING SYMBOL

Refactor code.

βž•

HEAVY PLUS SIGN

Add a dependency.

βž–

HEAVY MINUS SIGN

Remove a dependency.

πŸ”§

WRENCH

Add or update configuration files.

πŸ”¨

HAMMER

Add or update development scripts.

🌐

GLOBE WITH MERIDIANS

Internationalization and localization.

✏

PENCIL

Fix typos.

πŸ’©

PILE OF POO

Write bad code that needs to be improved.

βͺ

BLACK LEFT-POINTING DOUBLE TRIANGLE

Revert changes.

πŸ”€

TWISTED RIGHTWARDS ARROWS

Merge branches.

πŸ“¦

PACKAGE

Add or update compiled files or packages.

πŸ‘½

EXTRATERRESTRIAL ALIEN

Update code due to external API changes.

🚚

DELIVERY TRUCK

Move or rename resources (e.g.: files, paths, routes).

πŸ“„

PAGE FACING UP

Add or update license.

πŸ’₯

COLLISION SYMBOL

Introduce breaking changes.

🍱

BENTO BOX

Add or update assets.

β™Ώ

WHEELCHAIR SYMBOL

Improve accessibility.

πŸ’‘

ELECTRIC LIGHT BULB

Add or updates comments in source code.

πŸ—ƒ

CARD FILE BOX

Perform database related changes.

πŸ”Š

SPEAKER WITH THREE SOUND WAVES

Add or update logs.

πŸ”‡

SPEAKER WITH CANCELLATION STROKE

Remove logs.

πŸ‘₯

BUSTS IN SILHOUETTE

Add or update contributors.

🚸

CHILDREN CROSSING

Improve user experience / usability.

πŸ—

BUILDING CONSTRUCTION

Make architectural changes.

πŸ“±

MOBILE PHONE

Work on responsive design.

🀑

CLOWN FACE

Mock things.

πŸ₯š

EGG

Add or update an Easter Egg.

πŸ™ˆ

SEE-NO-EVIL MONKEY

Add or update a .gitignore

πŸ“Έ

CAMERA WITH FLASH

Add or update snapshots.

βš—

ALEMBIC

Perform experiments.

πŸ”

LEFT-POINTING MAGNIFYING GLASS

Improve SEO.

🏷

LABEL

Add or update types.

🌱

SEEDLING

Add or update seed files.

🚩

TRIANGULAR FLAG ON POST

Add, update or remove feature flags.

πŸ₯…

GOAL NET

Catch errors.

πŸ’«

DIZZY SYMBOL

Add or update animations and transitions.

πŸ—‘

WASTEBASKET

Deprecate code that needs to be cleaned up.

πŸ›‚

PASSPORT CONTROL

Work on code related to authorization, roles and permissions.

🩹

ADHESIVE BANDAGE

Simple fix for a non-critical issue.

🧐

FACE WITH MONOCLE

Data exploration / inspection.

⚰

COFFIN

Remove dead code.

πŸ§ͺ

TEST TUBE

Add a failing test.

πŸ‘”

NECKTIE

Add or update business logic.

🩺

STETHOSCOPE

Add or update health check.

🧱

BRICK

Infrastructure related changes.

About

Kumpels profile for the GitHub people

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published