A Pen by Sergio Uve on CodePen.
// NO? | |
validator.isValid() | |
? (this.status = Statuses.Valid) | |
: (this.status = Statuses.Invalid); | |
// YES? | |
this.status = validator.isValid() | |
? Statuses.Valid | |
: Statuses.Invalid; |
RGCIFUWWWTOEJBY or "Random Git Conventions I Found Useful While Working With Teams Or Even Just By Myself"
Each of this RGCIFUWWWTOEJBY's can be used by themselves or in combination with everything else.
As often as logically possible. I mean, commits are free of charge.
- Limit the message to 50 characters.
- Capitalize the first word.
- Use the imperative mode. As a rule a thumb, imagine you are trying to complete the phrase "When applied, this commit will ______".
Working with Git is easy. At the same time, it has enough depth and features to let you screw up your codebase at a considerable level. That's why the web is full of Git tutorials, blog posts and articles. That's also why a bunch of smart people have come up with certain Git workflows to avoid finding yourself lost in a sea of unmanageable changes. Let's dig into one of them.
As every decent Version Control System, Git has three core functionalities: store content, track changes to that content, and distribute the content and change history to possible collaborators. The way those changes are stored and organized is entirely up to the developer. This is going to be a very opinionated post about how to organize your Git workflow. I will explain how one these already existing workflow works, and introduce some small rules and changes on top of it. Said workflow is, obviosuly, Gitflow, created by Vincent Driessen.
F
date | work | chores | leisure | sleep | study | climb | run | outside | mood | |
---|---|---|---|---|---|---|---|---|---|---|
20190101 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | - | |
20190102 | 7 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | - | |
20190103 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | - | |
20190104 | 9 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | - | |
20190105 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | - | |
20190106 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | - | |
20190107 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | - | |
20190108 | 7 | 0 | 0 | 0 | 2.5 | 0 | 0 | 0 | - | |
20190109 | 8 | 2 | 1 | 4 | 0 | 2 | 0 | 0 | 7 |
- [PHP] It might FUCKING occur that in order to see code changes you have to restart the php-fpm service
- [GIT] Turns out Git allows you to have several push url for a single remote https://gist.github.com/bjmiller121/f93cd974ff709d2b968f
git remote set-url --add --push [remote] [original repo URL]
git remote set-url --add --push [remote] [second repo URL]
- No te pongas ahora a picar como un Zulú. | |
- Qué es una raya más en un tigre. | |
- Te explicas peor que un libro en llamas. | |
- No te tires los pedos más altos que el culo. | |
- Eso es la auténtica salud. | |
- Yo voy siempre a favor de obra. | |
- Has estado pensando fuera del recipiente. |
Music Worth Fighting For | |
--- | |
1. Red Hot Chili Peppers | |
2. The Police | |
3. The Rolling Stones | |
4. Crystal Fighters | |
5. Lera Lynn | |
6. Bob Dylan | |
7. Twenty One Pilots |
#!/usr/bin/env bash | |
# yodo installation script | |
cd | |
update=false | |
case "$OSTYPE" in | |
darwin*) echo 'export PATH="~/.yodo:$PATH"' >> ~/.bash_profile; source ~/.bash_profile ;; | |
linux*) echo 'export PATH="~/.yodo:$PATH"' >> ~/.bashrc; source ~/.bashrc; echo 'linux' ;; |
| (• ◡•)|╯╰( ❍ᴥ❍ ʋ ) |