As a freelancer, I build a lot of web sites. That's a lot of code changes to track. Thankfully, a Git-enabled workflow with proper branching makes short work of project tracking. I can easily see development features in branches as well as a snapshot of the sites' production code. A nice addition to that workflow is that ability to use Git to push updates to any of the various sites I work on while committing changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| .fullSundae{ | |
| height:500px; | |
| position:static; | |
| } | |
| .fullSundae > .iceCreamScoop{ | |
| height:100px; | |
| } | |
| .glass{ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Clone a specific branch from remote | |
| git clone -b <branch_name> <repository> | |
| <example> | |
| git clone -b development https://github.com/arkisoul/salstro.git | |
| Push a branch to a remote branch | |
| git push <remote_name> <local_branch>:<remote_branch> | |
| <example> | |
| git push origin master:development |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| A common use of mysqldump is for making a backup of an entire database: | |
| shell> mysqldump db_name > backup-file.sql | |
| You can load the dump file back into the server like this: | |
| UNIX | |
| shell> mysql db_name < backup-file.sql | |
| The same in Windows command prompt: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $primary-color: #EE6352; | |
| $youtube: #D16E8D; | |
| $articles: #FFAC83; | |
| $community: #3F78C9; | |
| $courses: #49C4A3; | |
| $white: #FFF; | |
| $black: #444A51; | |
| $lighten: 5; | |
| $darken: 25; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| def collatz_sequence(x): | |
| seq = [x] | |
| if x < 1: | |
| return [] | |
| while x > 1: | |
| if x % 2 == 0: | |
| x = x / 2 | |
| else: | |
| x = 3 * x + 1 | |
| # Added line |
- Capitalization and Punctuation: Capitalize the first word and do not end in punctuation. If using Conventional Commits, remember to use all lowercase.
- Mood: Use imperative mood in the subject line. Example – Add fix for dark mode toggle state. Imperative mood gives the tone you are giving an order or request.
- Type of Commit: Specify the type of commit. It is recommended and can be even more beneficial to have a consistent set of words to describe your changes. Example: Bugfix, Update, Refactor, Bump, and so on. See the section on Conventional Commits below for additional information.
- Length: The first line should ideally be no longer than 50 characters, and the body should be restricted to 72 characters.
- Content: Be direct, try to eliminate filler words and phrases in these sentences (examples: though, maybe, I think, kind of). Think like a journalist.
<type>[optional scope]: <description>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| class ContactFinder { | |
| #db; | |
| #chatToFind; | |
| #dbName = "model-storage"; | |
| #chatsCol = "chat"; | |
| #contactCol = "contact"; | |
| #groupCol = "participant"; | |
| constructor(chatGroupName) { | |
| this.#chatToFind = chatGroupName; |