• views: 80
• date: 7 April 2025
• posted by: AD-TEAM

When submitting a pull request to fix a bug, it's vital that a test accompanies your fix. The maintainer can't just take your word for it. Show them what the problem is. "Hey, if we take this specific route through the code, everything blows up. Here's a test that proves it."

How to Manage an Open Source Project
The GitHub Repository
Installation Instructions
Resolving Our First Issue
The Issue and PR Grind
Feature: Forum Reputation
Feature: Forum Reputation Refactoring
Feature: Displaying Reputation
Feature: Reducing Reputation
Licensing and Code of Conducts
Merging and Tweaking a Large PR
Continuous Integration
StyleCI
Syntax Highlighting PR With Refactoring
The Importance of Understanding a PR
Queues and Worker Bees
A Thread Can Be Pinned
Archiving Channels With TDD
Simpler Queries With Global Scopes
The Test Proves It's a Bug
Squashing and Merging the New UI
Upgrading to Laravel 5.6




   
   
   

Forex Trading

Crypto Trading. 20 USD Bonus after KYC

We need your support!
Make a donation to help us stay online
        
Bitcoin (BTC)
bc1q08g9d22cxkawsjlf8etuek2pc9n2a3hs4cdrld
	
Bitcoin Cash (BCH)
qqvwexzhvgauxq2apgc4j0ewvcak6hh6lsnzmvtkem

Ethereum (ETH)
0xb55513D2c91A6e3c497621644ec99e206CDaf239

Litecoin (LTC)
ltc1qt6g2trfv9tjs4qj68sqc4uf0ukvc9jpnsyt59u

USDT (ERC20)
0xb55513D2c91A6e3c497621644ec99e206CDaf239

USDT (TRC20)
TYdPNrz7v1P9riWBWZ317oBgJueheGjATm

0 1 2 3 4 5

| Print version |

	Information
		Users of GUESTS are not allowed to comment this publication.