[Extra] Use name convention (issue) and the same labels across repos

[furdzik]

This is not something to put in style guide, but it is something I want to do 😄

See, and create one set:

• https://github.com/furdzik/IF.Kamisama/labels
• https://github.com/furdzik/IF.Portfolio/labels
• https://github.com/furdzik/IF.Japanese/labels
• https://github.com/furdzik/IF.Frontend/labels
• https://github.com/furdzik/IF.Frontend.JobInterview/labels
• https://github.com/furdzik/IF.CSSArt/labels
• https://github.com/furdzik/IF.MasterThesisApp/labels

[furdzik]

[RECOMMENDATION]

GENERAL REPOS:

• dependencies - Pull requests that update a dependency file (color: #0446a9)
• documentation - Improvements or additions to documentation (color: #0066ff)
• issue - Bugs or problem to solve (color: #ff0000)
• feature - New functionality (color: #26E607)
• refactor - Improve quality of code (color: #5319E7)
• seciurity - Security problem (color: #ffcc00)
• tests - (color: #ff007d)
• user expirience - Improve UX (color: #CD2ACF)
• question - Question to ask the author (color: #53D9F7)

---

DOCS REPOS:

• consider - Consider a proposition (color: #ff4000)
• dependencies - Pull requests that update a dependency file (color: #0446a9)
• documentation - Improvements or additions to documentation (color: #0066ff)
• improve - Something to improve (color: #FBCA04)
• issue - Bugs or problem to solve (color: #ff0000)
• project - New project (color: #ff007d)
• proposition - Proposition of a solution (color: #D51EC7), if something is proposition can't be a recommendation
• recommendation - Recommendation of solution (color: #26E607), if something is proposition can't be a recommendation
• for interview - Preparation for the interview (color: #5319e7)
• e.g. [TYPE]: github - [desc type] for GitHub stuff (color: #53D9F7)
• [TYPE]: javascript - [desc type] for JavaScript (color: #53D9F7)
• [TYPE]: npm - [desc type] for NPM (color: #53D9F7)
• [TYPE]: react - [desc type] for React (color: #53D9F7)
• [TYPE]: redux and store - [desc type] for Redux and store (color: #53D9F7)
• [TYPE]: docs - [desc type] for Docs and Storybook (color: #53D9F7)
• [TYPE]: tests - [desc type] for tests (color: #53D9F7)
• [TYPE]: general - General [desc type] (color: #53D9F7)

* [TYPE] can be name of the repo or type of repo, e.g. FRONTEND: github, STYLE GUIDE: tests etc. * [desc type] can be description of type e.g. "Style guide for GitHub stuff" or "Knowledge of GitHub stuff"

[furdzik]

[RECOMMENDATION]

TITLES

Rules:

• all issues titles need to have label also with square brackets
• only one bracket label
• for documentation's repo issues only one TYPE label (with color: #53D9F7)

Titles names:

• [General] - very general description
• [TYPE] (type of language e.g. React, JavaScript, or e.g. in Job interview: Me, Interview, Company etc.)
• [Community] - Stack Overflow, contributing etc
• [Extra] - Something extra, e.g. something to not include in
• [Try]
• [Security]

If issue is concrete as [Style], [React], [Redux] or [Storybook] use this. If issue is less concrete, use more general description as [JavaScript] or even more general [General].

[furdzik]

[RECOMMENDATION]

• renaming problem to: issue or bug

[furdzik]

[RECOMMENDATION]

• Always use one way of creating: propositions, recommendations, things to consider
• Add this also to docs

**[PROPOSITION / RECOMMENDATION / CONSIDER / TODO *]**

Message

* Choose only one

[furdzik]

[TODO]

Public recommendation in README as Extras