DannyDannyDanny/gitmoji

Repo Roadmap

• 2021Q1: Gitmoji -> (general) Methodology
• 2021Q2: Git Methodology -> Branching, Merging and Pull Requests
• 2021Q3: Organize other methodology better
• 2021Q4: Add collaborators

This methodology repo is focused on Python Data Processing based projects with som external dependencies (APIs or DBs). In your commit message use the format :gitmoji: <commit message>. Only propper nouns, CamelCase and class names should have uppercases letters. Avoid using multiple gitmojis.

gitmoji Lookup

emoji	code	description
✨	:sparkles:	add new feature / function
🎨	:art:	improve readibility / structure and lint flake8
🥅	:goal_net:	try/raise/handle errors or warnings
⚡	:zap:	improve performance / coverage / profiling
🐛	:bug:	fix this bug
🚚	:truck:	moving / renaming
♻️	:recycle:	refactor code
🚧 / 💥	:construction:/:boom:	work in progress / breaking changes
✅	:white_check_mark:	writing tests, running tests
📝	:memo:	doc / logging / verbosity / code comments
🔥	:fire:	remove code / file
👽	:alien:	changes related to APIs and Databases
📊	:bar_chart:	clean / transform / validate data
💄	:lipstick:	improve UI / UX, CLI or visualizations
📌	:pushpin:	Dependency and environment versioning
🙈	:see_no_evil:	changes to .gitignore and exclusively local files

Missing a gitmoji? Get inspiration. Submit an issue (or Pull Request).

Other methdology

• Things you should do know
• Follow naming conventions
• Use scrum methodology
• Do CodeReviews
• Use databases
  • Consider SQL (but don't use select *)
• Avoid dark patterns
• Security
  • Audit security
  • Understand SSH tunnels
• Use non-linear roadmaps
• Use solarized-theme
  • git bash solarized 🌞